Expired Tokens stay in Database when using MySQL Backend
Bug #1155709 reported by
Emilien Macchi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
This is a bug which needs a new feature. That's why I link it to a blueprint.
Environment :
- OpenStack Grizzly
- Keystone with MySQL Backend for token storage
Bug :
Expired tokens stay in Database.
In Public Cloud, that could be a problem when a lot of tokens are asked every time (and even in Private Cloud).
(Possible) Solution :
add a flag in keystone.conf like :
keep_expired_tokens = True
retention_time = 365 #in days
| description: | updated |
Revision history for this message
| Dolph Mathews (dolph) wrote | #1 |
| Changed in keystone: | |
| status: | New → Invalid |
To post a comment you must log in.
A similar proposal is also being tracked in a different blueprint:
https:/
Closing this bug as the two blueprints are sufficient for tracking.