Bug 1462048 - [RFE] API Keys/Application specific passwords
[RFE] API Keys/Application specific passwords
Status: POST
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-keystone (Show other bugs)
12.0 (Pike)
Unspecified Unspecified
medium Severity medium
: Upstream M2
: 14.0 (Rocky)
Assigned To: John Dennis
: FutureFeature, TestCaseNeeded, Triaged
Depends On:
  Show dependency treegraph
Reported: 2017-06-15 20:55 EDT by Graeme Gillies
Modified: 2018-07-16 13:26 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: Application Credential are now supported Reason: Result: https://docs.openstack.org/keystone/latest/user/application_credentials.html
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 450415 None None None 2018-06-28 16:35 EDT
OpenStack gerrit 534965 None None None 2018-06-28 16:40 EDT
OpenStack gerrit 552145 None None None 2018-06-28 16:40 EDT
OpenStack gerrit 559429 None None None 2018-06-28 16:41 EDT

  None (edit)
Description Graeme Gillies 2017-06-15 20:55:27 EDT
This RFE is to enable/implement the following



in RHOS.

Not only does work need to be done in keystone, but also openstack client and horizon as well (for best user experience).
Comment 13 Harry Rybacki 2018-06-28 16:40:25 EDT
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/

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