Bug 1042218 - [RFE][heat]: Allow Keystone Trusts in API request headers
Summary: [RFE][heat]: Allow Keystone Trusts in API request headers
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/heat...
Whiteboard: upstream_milestone_next upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 21:23 UTC by RHOS Integration
Modified: 2016-02-08 17:23 UTC (History)
2 users (show)

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

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

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
Note You need to log in before you can comment on or make changes to this bug.