Bug 1826534

Summary: Support 'openstack keypair list --project'
Product: Red Hat OpenStack Reporter: David Vallee Delisle <dvd>
Component: python-openstackclientAssignee: Stephen Finucane <stephenfin>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: medium Docs Contact:
Priority: low    
Version: 16.1 (Train)CC: apevec, dasmith, egallen, eglynn, jhakimra, jpichon, jschluet, jzaher, kchamart, lhh, mircea.vutcovici, sbauza, sgordon, stephenfin, vromanso
Target Milestone: ---Keywords: Patch, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-openstackclient-5.5.1-0.20220427021748.53f1efa.el9ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-09-21 12:09:43 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: Wallaby
Embargoed:

Description David Vallee Delisle 2020-04-21 22:13:08 UTC 
Description of problem:
There's some situation where it would be easier for the admin user to list and/or delete all keypairs. While we understand that it wasn't implemented because some people might see this as a security issue, I think we should consider the fact that we never see or even store the private key.

Also, the admin user can normally access the database and get the information, forcing them to bypass the CLI, or use this kind of hack [1]

[1] https://orchestration.io/2016/03/14/listing-all-key-pairs-in-openstack/
Comment 6 Stephen Finucane 2020-11-09 15:41:06 UTC 
This has been accepted upstream and should be included in a future 5.5.0/6.0 release.
Comment 16 errata-xmlrpc 2022-09-21 12:09:43 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 (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), 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-2022:6543