Bug 1041916

Summary:	[RFE][keystone]: Issue identity scoped (unscoped) token if default project is invalid
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/keystone/+spec/unscoped-token-for-invalid-default-project
Whiteboard:	upstream_milestone_none upstream_status_not-started upstream_definition_superseded
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 16:50:52 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:03:31 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/unscoped-token-for-invalid-default-project.

Description:

It would be nice to have a fail-safe mechanism for default project scoping. Right now, if default project is set, user will locked out if default project is disabled or deleted. Default project was meant to provide user to convenience to set the default scope when interactive with UI.  We need to give user a chance to log back into the UI and change the default project setting when that happens.

Specification URL (additional information):

None