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"/>
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"?> docs.openstack. org/identity/ api/v2. 0"> "2010-11- 01T03:32: 15-05:00" db23ty3494" /> docs.openstack. org/identity/ api/v2. 0"> store:admin" tenantId="1"/>
<access xmlns="http://
<token expires=
id="ab48a9efdfe
<user id="123" username="jqsmith">
<roles xmlns="http://
<role id="123" name="Admin" tenantId="one"/>
<role id="234" name="object-
</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" db23ty3494" />
id="ab48a9efdfe