Pre-cache new tokens for 5 minutes
Registered by
Alexander Makarov
keystonemiddleware can use shared cache for validated tokens. We can save a lot of first time validations if we put all new tokens in the same cache on the server side right after it is issued.
We cannot use memoize decorator here as cache should be populated by results of token issue and requested upon token validation. So cache should be addressed explicitly.
Blueprint information
- Status:
- Complete
- Approver:
- Steve Martinelli
- Priority:
- Medium
- Drafter:
- Alexander Makarov
- Direction:
- Approved
- Assignee:
- Alexander Makarov
- Definition:
- Approved
- Series goal:
- Accepted for newton
- Implementation:
- Implemented
- Milestone target:
- newton-3
- Started by
- Steve Martinelli
- Completed by
- Steve Martinelli
Related branches
Related bugs
Sprints
Whiteboard
(stevemar 4/12/2016) this was discussed in a keystone meeting, will link to logs.
Refer to http://
Gerrit topic: https:/
Addressed by: https:/
Pre-cache new tokens
(?)