Bug 1041942 - [RFE][keystone]: periodically flush expired token
Summary: [RFE][keystone]: periodically flush expired token
Keywords:
Status: CLOSED UPSTREAM
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:12 UTC by RHOS Integration
Modified: 2015-03-19 17:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:05:53 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description RHOS Integration 2013-12-12 20:12:06 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/periodically-flush-expired-token.

Description:

Now we need the deployer to add a cron-like job to call 'keystone-manage token_flush' to remove the expired token records in the token backend (kvs, mysql, memcache, etc) so that the token persistence mechanism will not be filled up with expired tokens.

This BP adds a periodic thread in keystone-all process, which will run at a configurable interval to flush the expired token from DB. The interval should be configured more than CONF.token.expiration (86400). If the configured value is no more than 0, the periodic thread will not run.

It also flushes the oauth token.

Specification URL (additional information):

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