Bug 1041946 - [RFE][keystone]: reuse valid token
Summary: [RFE][keystone]: reuse valid token
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/keys...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 20:13 UTC by RHOS Integration
Modified: 2015-03-09 01:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-09 01:15:05 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 20:13:39 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/reuse-token.

Description:

Now if we call the auth API with the same authentication information, the keystone will always return a new token.  This behavior sometimes will bloat the token table with valid tokens when the auth API is called too often and the expiration time is long.

This BP tries to reuse the same token when the existing token has the same scope as the expected new one. We try to reuse the existing token if the expiry time is within a scope ( threshold). We will not change the reused token's expiry time, i.e. we return the old token as it is.

the IRC discussion logs:
https://docs.google.com/document/d/1RUARZCQzbS4QnXV3Mod3ZLg9oj-oHR_kR0S6APiVk1A/edit?usp=sharing

Specification URL (additional information):

None

Comment 2 Jamie Lennox 2015-03-09 01:15:05 UTC
This blueprint was rejected in favour of having non-persistent tokens.


Note You need to log in before you can comment on or make changes to this bug.