Create Application Credential not appearing in Horizon

Pierre Riteau pierre at stackhpc.com
Tue Sep 8 14:18:14 UTC 2020


Hi Alex,

In addition to adding this setting to Keystone's policy file, does Horizon
have its own copy of the keystone policy file accessible and including
these settings? By default it is named keystone_policy.json.

Best wishes,
Pierre

On Tue, 8 Sep 2020 at 14:48, Alexander Dibbo - UKRI STFC <
alexander.dibbo at stfc.ac.uk> wrote:

> Hi All,
>
>
>
> I’m having an issue where users with the “user” role in my deployment are
> not seeing the “Create Application Credential” button in horizon although
> users with the “admin” role can.
>
>
>
> I have tried modifying the keystone policy a couple of different ways to
> fix this but none have worked:
>
> "identity:create_application_credential": "user_id:%(user_id)s",
>
> "identity:create_application_credential": "role: user",
>
> "identity:create_application_credential": "rule:owner",
>
> "identity:create_application_credential": "",
>
>
>
> Could anyone point me in the right direction?
>
>
>
> My deployment is running the Train release of OpenStack
>
>
>
> Thanks,
>
>
>
> Alex
>
>
>
>
>
> Regards
>
>
>
> Alexander Dibbo – Cloud Architect / Cloud Operations Group Leader
>
> For STFC Cloud Documentation visit https://stfc-cloud-docs.readthedocs.io
>
> To raise a support ticket with the cloud team please email
> cloud-support at gridpp.rl.ac.uk
>
> To receive notifications about the service please subscribe to our mailing
> list at: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=STFC-CLOUD
>
> To receive fast notifications or to discuss usage of the cloud please join
> our Slack: https://stfc-cloud.slack.com/
>
>
>
> This email and any attachments are intended solely for the use of the
> named recipients. If you are not the intended recipient you must not use,
> disclose, copy or distribute this email or any of its attachments and
> should notify the sender immediately and delete this email from your
> system. UK Research and Innovation (UKRI) has taken every reasonable
> precaution to minimise risk of this email or any attachments containing
> viruses or malware but the recipient should carry out its own virus and
> malware checks before opening the attachments. UKRI does not accept any
> liability for any losses or damages which the recipient may sustain due to
> presence of any viruses. Opinions, conclusions or other information in this
> message and attachments that are not related directly to UKRI business are
> solely those of the author and do not represent the views of UKRI.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200908/40700e98/attachment.html>


More information about the openstack-discuss mailing list