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 "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
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
*Yogeshwar Srikrishnan*
Software Engineer III
Email: [email protected]
<mailto:[email protected]>
Phone: (210) 459-1412
This email may include confidential information. If you received it in error,
please delete it.
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
