Bug 1041946

Summary: [RFE][keystone]: reuse valid token
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: jlennox, markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/keystone/+spec/reuse-token
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_superseded
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-09 01:15:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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.