[keystone] anyone using OpenID with Keystone?
knikolla at bu.edu
Wed Feb 16 14:23:34 UTC 2022
Would application credentials fit your use case for CLI access? Users will be able to create them through Horizon, and after creation they will be prompted to download either a clouds.yaml or an openrc file, so the process is pretty straightforward.
Can you elaborate more on your issue with not being able to grant roles to groups?
On Feb 15, 2022, at 05:49, Francois <rigault.francois at gmail.com<mailto:rigault.francois at gmail.com>> wrote:
Hi Keystone users!
I am wondering if anyone has experience with keystone openid integration.
Initially I was using Keystone LDAP backend (using tripleo
KeystoneLDAPDomainEnable and KeystoneLDAPBackendConfigs parameters)
and it works! Users are able to log in through Horizon or through the
cli, roles can be given per LDAP group, and you can click in Horizon
and download a working openrc or clouds.yaml file (minus the root CA
that has to be added) to authenticate with the cli (and your password
ends as an OS_PASSWORD variable in your environment).
I am now trying the Keystone Openid backend (using the
enable-federation-openidc.yaml provided by tripleo -
with a mapping like this:
The SSO works superb with Horizon, however
- logging with the cli seems impractical. I see some doc here:
where you need to provide a secret, I am skeptical I want to do that.
The openrc file downloaded from Horizon is not usable as is and needs
some tuning. And there is no SSO, and the password still ends up in
- I don't see how I can grant roles to groups anymore. It seems I need
an extra mechanism to grant permissions (as I used to do that using
I am wondering if anyone is willing to share their experience dealing
with Keystone and OpenID.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss