<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">So agree with Dolph's comment - and what you'll find is that a domain qualifier will be included when you need it, for example:<div><br></div><div>X_USER_DOMAIN_ID</div><div><br></div><div>will be present in a v3 token because you made need it to qualify which domain a user is in to correctly identify them. In v2 token you know the user name is unique by definition. So if there is no X_USER_DOMAIN_ID defined in the token, then you know you can use user name on its own safely.</div><div><br></div><div>See the doc info at the top of auth_token if keystoneclient/middleware for a more details description.</div><div><br></div><div>Henry<br><div><br></div><div><div><div>On 21 Mar 2013, at 16:17, Dolph Mathews wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">X_TENANT_ID should be deprecated in favor of X_PROJECT_ID, and the values should be equivalent. The same applies to *_NAME.<div><br></div><div>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!<br>
<div><div class="gmail_extra"><div><div><br></div>-Dolph</div>
<br><br><div class="gmail_quote">On Tue, Mar 12, 2013 at 3:39 AM, Chmouel Boudjnah <span dir="ltr"><<a href="mailto:chmouel@chmouel.com" target="_blank">chmouel@chmouel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi,<br>
<br>
I see that this review has been merged:<br>
<br>
<a href="https://review.openstack.org/#/c/23401/" target="_blank">https://review.openstack.org/#/c/23401/</a><br>
<br>
and while thinking about the integration with (swift middleware)<br>
keystoneauth I was wondering what would be the best way for a<br>
middleware that goes after auth_token to detect which version of<br>
keystone API we are authing.<br>
<br>
We can always check for X_PROJECT/TENANT variable to know what<br>
keystone server version auth_token was authenticating to but what<br>
about instead a X_AUTH_VERSION there to make it easier ?<br>
<br>
<br>
Chmouel.<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div></div></div></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></div></div></body></html>