OpenStack Identity (keystone)

Force new token in Swift authentication

Asked by André Cruz

I'm evaluating keystone in order to check if it resolves an issue I have with Swift's tempauth. Basically I cannot request a new token for a user until the existing token has expired. This means that in a scenario where I'm constantly interacting with Swift I am bound to get a 401 error when the token I'm using expires. Since I cannot issue a retry, this is a problem for me since that request is lost. Does keystone have the same issue? Can I force the creation of new tokens? Is there another way to deal with this issue not involving retries?

Thanks.

Question information

Language:
English Edit question
Status:
Answered
For:
OpenStack Identity (keystone) Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Joseph Heck (heckj) said : 		#1

André,

The current implementation of Keystone doesn't limit the tokens it hands out to end-users based on the existence of other tokens, in fact, if anything it's too prolific and happily generates new tokens as they're requested when the API call to POST /token comes in.

Can you help with this problem?

Provide an answer of your own, or ask André Cruz for more information if necessary.

To post a message you must log in.