Bug 1462048
Summary: | [RFE] API Keys/Application specific passwords | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Graeme Gillies <ggillies> |
Component: | openstack-keystone | Assignee: | John Dennis <jdennis> |
Status: | CLOSED ERRATA | QA Contact: | Pavan <pkesavar> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 12.0 (Pike) | CC: | hrybacki, jamsmith, kbasil, nkinder, panbalag, rcritten, sclewis, srevivo |
Target Milestone: | Upstream M2 | Keywords: | FutureFeature, TestCaseNeeded, Triaged |
Target Release: | 14.0 (Rocky) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-keystone-14.0.0-0.20180805135729 | Doc Type: | Enhancement |
Doc Text: |
With this update, Users can create application credentials to allow their applications to authenticate to keystone.
See https://docs.openstack.org/keystone/latest/user/application_credentials.html
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-01-11 11:47: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: | 1659296 |
Description
Graeme Gillies
2017-06-16 00:55:27 UTC
Support for application credentials within the python-keystoneclient landed towards the end of the Queens release[1]. The blueprint to add functionality in Horizon was approved for Rocky[2] and is being worked in the following reviews[3,4] both of which have merged. [1] - https://review.openstack.org/#/c/534965/ [2] - https://blueprints.launchpad.net/horizon/+spec/application-credentials [3] - https://review.openstack.org/#/c/552145/ [4] - https://review.openstack.org/#/c/559429/ Required bits have landed downstream. Review session with QE complete. Noting FIV and moving bug to MODIFIED. 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. https://access.redhat.com/errata/RHEA-2019:0045 |