Bug 1042218

Summary:	[RFE][heat]: Allow Keystone Trusts in API request headers
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/heat/+spec/x-auth-trust
Whiteboard:	upstream_milestone_next upstream_status_not-started upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:33:35 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 21:23:45 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/x-auth-trust.

Description:

Heat uses Keystone Trusts to support autoscaling. But trust cannot be provided through API call - either a "not-trust-scoped" auth token or user credentials have to be specified in request headers. If client applications could provide trusts directly in requests, they could manage user stacks automatically, without knowing user credentials.

Specification URL (additional information):

None