Bug 989681 - [RFE] Ensure heat works when only an auth_token is specified
Summary: [RFE] Ensure heat works when only an auth_token is specified
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-heat
Version: 4.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: Upstream M3
: 4.0
Assignee: Steve Baker
QA Contact: Steven Hardy
URL: https://blueprints.launchpad.net/heat...
Whiteboard:
Depends On:
Blocks: RHOS40RFE
TreeView+ depends on / blocked
 
Reported: 2013-07-29 17:33 UTC by Steven Hardy
Modified: 2013-12-20 00:16 UTC (History)
9 users (show)

Fixed In Version: openstack-heat-2013.2-0.8.b3.el6ost
Doc Type: Enhancement
Doc Text:
The Orchestration service now accepts existing Keystone tokens, which Heat can use to interact with the underlying services. By default, python-heatclient now creates a token on your behalf, which is then passed to the Heat API. Alternatively, you can specify an existing token via the '--os-auth-token' option. Token support in Heat allows enhanced security over simple username/password authentication. This feature also reduces Keystone token generation, thereby reducing Identity service overhead.
Clone Of:
Environment:
Last Closed: 2013-12-20 00:16:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2013:1859 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2013-12-21 00:01:48 UTC

Comment 2 Steven Hardy 2013-09-18 12:42:39 UTC
Merged for h3, setting status to POST:

https://blueprints.launchpad.net/heat/+spec/auth-token-only

Comment 5 Steven Hardy 2013-11-26 21:57:40 UTC
I did some testing related to this recently, and found a number of issues related to token-only auth via python-heatclient:

https://bugs.launchpad.net/python-heatclient/+bug/1252248

Patches proposed but not yet merged:

https://review.openstack.org/#/q/status:open+project:openstack/python-heatclient+branch:master+topic:bug/1252248_2,n,z

The heat API aspects all seem to work OK AFAICT, the issues were only in the client code, so we need to decide if this bug covers both of if we need a new bz tracking the client issues.

Comment 6 Steven Dake 2013-11-26 22:14:03 UTC
Since the bug is in the component openstack-heat and the bug you linked in your recent testing is in the component python-heatclient, a new bug is necessary.

Comment 7 Steven Hardy 2013-11-27 09:40:35 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=1035199 raised for python-heatclient issues mentioned above

Comment 9 Steven Hardy 2013-12-16 15:40:57 UTC
Doc Text updated.

Comment 12 errata-xmlrpc 2013-12-20 00:16:34 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.

http://rhn.redhat.com/errata/RHEA-2013-1859.html


Note You need to log in before you can comment on or make changes to this bug.