Keystone token reuse
Keystone issues new tokens for every authentication request. This can lead to excessive tokens that are sitting around that are not yet expired but are also not being used any further.
An option should be created that would allow a keystone service to provide the active token for a user when they authenticate. This would also solve scenarios where scripts, or other openstack components (see https:/
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Matthew J Black
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Morgan Fainberg
Related branches
Related bugs
Sprints
Whiteboard
This has been discussed over and over again and is unlikely to occur. There are other approaches to solving the token issue(s) that are under development: Non-persistent tokens is the key one. There will also be discussion at the Kilo design summit specifically targeted at solving issues with tokens.
