Bug 1041880 - [RFE][keystone]: Periodically flush the expired tokens
Summary: [RFE][keystone]: Periodically flush the expired tokens
Keywords:
Status: CLOSED CURRENTRELEASE
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 19:51 UTC by RHOS Integration
Modified: 2014-10-21 04:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 12:45:04 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 19:51:40 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/keystone-manage-token-flush-periodically.

Description:

With the H release, keystone-manage  has a new parameter called "token_flush" to flush the expired tokens (see https://blueprints.launchpad.net/keystone/+spec/keystone-manage-token-flush).
This is still a manual task which needs to be done by operations. 

There should be a periodic task in keystone to flush the expired tokens automatically.

I propose to add a new config parameter to the [token] section called "flush_period". This value is an integer (in seconds). If 0, the automatic flushing is disabled. So a possible keystone.conf looks like:

[token]
...
flush_period=3600
...

With this configuration, the expired tokens are every hour deleted.
To implement this, a ThreadGroup.add_timer() from openstack.common can be used.

Specification URL (additional information):

None

Comment 2 Nathan Kinder 2014-08-06 12:45:04 UTC
Havana/RHOS4 and later already sets up the token_flush operation as a cron job.  Closing this as CURRENTRELEASE.


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