[openstack-dev] [Keystone] v3 auth_token and version

Dolph Mathews dolph.mathews at gmail.com
Thu Mar 21 16:17:07 UTC 2013


X_TENANT_ID  should be deprecated in favor of X_PROJECT_ID, and the values
should be equivalent. The same applies to *_NAME.

I'm curious what the use case is for detecting which API is in use? If you
need to distinguish between them, then we probably did something wrong!

-Dolph


On Tue, Mar 12, 2013 at 3:39 AM, Chmouel Boudjnah <chmouel at chmouel.com>wrote:

> Hi,
>
> I see that this review has been merged:
>
> https://review.openstack.org/#/c/23401/
>
> and while thinking about the integration with (swift middleware)
> keystoneauth I was wondering what would be the best way for a
> middleware that goes after auth_token to detect which version of
> keystone API we are authing.
>
> We can always check for X_PROJECT/TENANT variable to know what
> keystone server version auth_token was authenticating to but what
> about instead a X_AUTH_VERSION there to make it easier ?
>
>
> Chmouel.
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130321/c8c7c50b/attachment.html>


More information about the OpenStack-dev mailing list