Bug 989681
| Summary: | [RFE] Ensure heat works when only an auth_token is specified | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Steven Hardy <shardy> |
| Component: | openstack-heat | Assignee: | Steve Baker <sbaker> |
| Status: | CLOSED ERRATA | QA Contact: | Steven Hardy <shardy> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | CC: | ajeain, ddomingo, hateya, mlopes, sbaker, sdake, sgordon, shardy, yeylon |
| Target Milestone: | Upstream M3 | Keywords: | FutureFeature, OtherQA |
| Target Release: | 4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://blueprints.launchpad.net/heat/+spec/auth-token-only | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-20 00:16:34 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 975499 | ||
|
Description
Steven Hardy
2013-07-29 17:33:05 UTC
Merged for h3, setting status to POST: https://blueprints.launchpad.net/heat/+spec/auth-token-only 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. 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. https://bugzilla.redhat.com/show_bug.cgi?id=1035199 raised for python-heatclient issues mentioned above Doc Text updated. 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 |