Ask Your Question

Force new token in Swift authentication

asked 2012-07-03 16:14:29 -0500

andrefcruz gravatar image

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?


edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted

answered 2012-07-09 16:16:29 -0500

heckj gravatar image


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.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2012-07-03 16:14:29 -0500

Seen: 186 times

Last updated: Jul 09 '12