Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1196013

Summary:	[RFE][keystone]: Keystone Fernet (Lightweight) Tokens
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-keystone	Assignee:	Nathan Kinder <nkinder>
Status:	CLOSED ERRATA	QA Contact:	yeylon <yeylon>
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	ayoung, markmc, nbarcet, srevivo, ssainkar, yeylon
Target Milestone:	Upstream M3	Keywords:	FutureFeature, OtherQA
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/keystone/+spec/klw-tokens
Whiteboard:	upstream_milestone_kilo-3 upstream_definition_approved upstream_status_implemented
Fixed In Version:	openstack-keystone-2015.1.0-1.el7ost	Doc Type:	Enhancement
Doc Text:	The Identity service now has an experimental support for a new token format called 'fernet'. The token formats currently supported by the Identity service require issued tokens to be persisted in a database table. This table can grow quite large, which requires proper tuning and a flush job to keep the Identity service performing well. The new 'fernet' token format is designed to allow the token database table to be eliminated, avoiding the problem of this table becoming a scalability limitation. The 'fernet' token format is now available as an experimental feature.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:22:00 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2015-02-25 05:04:48 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/klw-tokens.

Description:

KLWT tokens provide a way to represent a token, allowing for tokens to be non-persistent. KLWT tokens provide integrity and confidentiality, when optionally using encryption, by being signed by Keystone. KLWT tokens contain some amount of token information, including the user, the issued at time, the expiration time, and the digest of the signed information. Regardless if encryption is used, the tokens are authentic since they are signed and validated by Keystone.

Specification URL (additional information):

https://github.com/openstack/keystone-specs/blob/master/specs/kilo/klwt.rst

Comment 3 Arthur Berezin 2015-03-22 12:58:10 UTC

This functionality is marked upstream as "Experimental",Marking as Technology Preview for OSP7.

Comment 10 errata-xmlrpc 2015-08-05 13:22:00 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1548