Ah. I’d let Tom or Ramana weigh in on that. IIRC, the access key is plaintext, 
so, I thought it can be displayed; that’s what the CLI is doing.
Reading the spec though, this was an intended part of the feature: 
http://specs.openstack.org/openstack/manila-specs/specs/newton/auth-access-keys.html


From: Arne Wiebalck <arne.wieba...@cern.ch>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Date: Thursday, November 3, 2016 at 10:15 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [manila] Access key via the UI?

Hi Goutham,

It’s already being returned in the manila access-list API as of 2.21, if you’re 
using the latest python-manilaclient, you should have it there. However, it’s 
missing in the UI:

Yes, I was comparing what I can do on the CLI and what was offered with the UI.


https://github.com/openstack/manila-ui/blob/c986a100eecf46af4b597cdcf59b5bc1edc2d1b0/manila_ui/dashboards/project/shares/shares/tables.py#L278

Are you suggesting to simply display it? (I was more thinking of a one-time 
download when giving access,
similar to what is offered for keys for instance creation.)


Could you open a bug?

Just did it:
https://bugs.launchpad.net/manila-ui/+bug/1638934

Thanks!
 Arne




On 11/3/16, 7:32 AM, "Arne Wiebalck" 
<arne.wieba...@cern.ch<mailto:arne.wieba...@cern.ch>> wrote:

   Hi,

   As cephx has been added as an access type in the dashboard and an access key 
can now
   be part of the API's response to access list requests, is it planned to have 
the access key to
   be returned when adding a cephx access rule via the UI (for instance similar 
to what ‘Create
   Key Pair’ in the instance panel does)? Couldn’t find any mention of such an 
activity.

   Thanks!
    Arne

   --
   Arne Wiebalck
   CERN IT

   __________________________________________________________________________
   OpenStack Development Mailing List (not for usage questions)
   Unsubscribe: 
openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe
   http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
Arne Wiebalck
CERN IT


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to