[Openstack] [OpenStack][Keystone]Does legacy_auth v1.0 exist in Keystone Essex ?

Rafael Durán Castañeda rafadurancastaneda at gmail.com
Thu May 24 11:55:21 UTC 2012


Re-sending to list, since I think I've got this by mistake:

On 05/24/2012 12:42 PM, Kuo Hugo wrote:
> *Thanks for all . *
> *
> *
> *I checked several parts of legacy_auth. *
> *
> *
> *There're some requirements of legacy_auth. We do not want to hack 
> exist essex code though. *
> *
> *
> *We're considering to add a filter in keystone's pipline. While the 
> API point to /v1.0 . Route to /v2.0/tokens . And transfer incoming 
> headers to a json format. *
> *After that , the middle-ware retrieve token and swift-proxy 
> public_url transfer into *
> *X-AUTH-TOKEN*
> *and *
> *X-Storage-Url *
> *return to user. *
> *
> *
> *But there's still has an issue. what should be the tenant of /v1.0 
> request? *
> *
> *
> *In Legacy_AUTH , the user's default tenant associate with user under 
> Users table. *
> *
> *
> *Should we keep this method , or pick up the first one tenant of user 
> from Essex's metadata table?*
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120524/7d14fd7f/attachment.html>


More information about the Openstack mailing list