Revision history [back]

click to hide/show revision 1
initial version

Keeping original scope when requesting a new token from token

Is there a way to tell Keystone that the scope of the new token requested (when using "token" as authentication method) is the same as the presented token?

In other words, in the absence of a "scope" attribute in the new request, can Keystone be hinted at using the same scope as the original?