Bug 1121844

Summary:	[RFE][keystone]: Explicitly request an unscoped token
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:	medium
Version:	unspecified	CC:	ayoung, markmc, mlopes, nbarcet, srevivo, yeylon
Target Milestone:	Upstream M2	Keywords:	FutureFeature, OtherQA
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/keystone/+spec/explicit-unscoped
Whiteboard:	upstream_milestone_kilo-2 upstream_definition_approved upstream_status_implemented
Fixed In Version:	openstack-keystone-2015.1.0-1.el7ost	Doc Type:	Enhancement
Doc Text:	Identity Service (keystone) now allows for unscoped tokens to be explicitly requested. This feature was added after users who had a default project assigned were previously unable to retrieve unscoped tokens; if one of these users requested a token without defining a scope, it would be automatically scoped to the default project. As a result of this update, unscoped tokens can now be issued to all users, even if they have a default project defined.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:13:07 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 2014-07-22 04:06:17 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/explicit-unscoped.

Description:

Allow users with a default_project_id set to explicitly ignore their default parameter and retrieve an unscoped token. 

Specification URL (additional information):

None

Comment 8 errata-xmlrpc 2015-08-05 13:13:07 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