GET /tokens/:id should not have a root of "access"

[Ziad Sawalha]

The response should be just the token object. The "access" at the root of the response for the POST is only for that call which returns more than the token.

[Yogeshwar (yogesh-srikrishnan)]

v2.0/tokens/{tokenId}?belongsTo=string => This is how the call is structured right now.
Current response as per our doc is

<?xml version="1.0" encoding="UTF-8"?>
<access xmlns="http://docs.openstack.org/identity/api/v2.0">
<token expires="2010-11-01T03:32:15-05:00"
id="ab48a9efdfedb23ty3494"/>
<user id="123" username="jqsmith">
<roles xmlns="http://docs.openstack.org/identity/api/v2.0">
<role id="123" name="Admin" tenantId="one"/>
<role id="234" name="object-store:admin" tenantId="1"/>
</roles>
</user>
</access>

Are we not going to return the user and roles block? Would the response just have

<token expires="2010-11-01T03:32:15-05:00"
id="ab48a9efdfedb23ty3494"/>

[Carlos Marin (carlos-marin-d)]

If response is going to be:

 <token expires="2010-11-01T03:32:15-05:00" id="ab48a9efdfedb23ty3494"/>

we'll need to update the token XSD.

[Yogeshwar (yogesh-srikrishnan)]

I dont think we would stop returning user and roles when a validate token call is made.
This what I think the response would be in case we want the call to return the roles as well

<token expires="2010-11-01T03:32:15-05:00"
id="ab48a9efdfedb23ty3494">
<user id="123" username="jqsmith">
<roles xmlns="http://docs.openstack.org/identity/api/v2.0">
<role id="123" name="Admin" tenantId="one"/>
<role id="234" name="object-store:admin" tenantId="1"/>
</roles>
</user>
</roles>
</token>
I have locally done the xsd changes.Iam waiting for Ziad to confirm.

[Dolph Mathews (dolph)]

While I'm in favor of this change as an improvement to /tokens in general, it also illustrates the growing scope bloat of the /tokens resources.

[Joe Savak (jsavak)]

wait on essex for this - b/c nova client is working against the old method. Not for diablo.

[Ziad Sawalha (ziad-sawalha)]

I'm not suggesting we don't return the user or roles blocks. I just think that they should be under/inside the token block. Since I am doing a get on tokens, I should be getting back a token. And the user and roles blocks are data about the user OF the token and the roles that ONLY THIS TOKEN is granting.

[Yogeshwar (yogesh-srikrishnan)]

/post on token => should it also return Token just to be consistent and not access?
Some one is doing a POST on token and getting back access just like this case.

[Joe Savak (jsavak)]

Yogi - yes - it should be consistent between the two

[Yogeshwar (yogesh-srikrishnan)]

Would be changing the XSD and WADL first.This change would also affect all the existing middleware components.Have started working.

[Yogeshwar (yogesh-srikrishnan)]

Looks like API change.Would take it for the next minor API change.