On Mon, Aug 15, 2011 at 6:44 PM, Nguyen, Liem Manh wrote:
> Currently, we have the legacy_token_auth to “help” with integration with
> services (like Swift) that still talks auth v1.0. Will this filter go away
> and other services will be speaking pure Keystone when Diablo releases?
It would ki
If you don't want legacy token auth as a middleware you should still be
able to edit keystone.conf and remove legacy-auth from the pipeline and
have the application running.
Regards
On 08/15/2011 06:44 PM, Nguyen, Liem Manh wrote:
Hello Stackers,
Currently, we have the legacy_token_auth to "
Hello Stackers,
Currently, we have the legacy_token_auth to "help" with integration with
services (like Swift) that still talks auth v1.0. Will this filter go away and
other services will be speaking pure Keystone when Diablo releases?
Thanks,
Liem
_
3 matches
Mail list logo