Keystone LDAP integration
- OpenStack Charmers
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/edge | 3 | 23 Oct 2023 | |
| 2024.1/beta | 50 | 11 Dec 2024 | |
| 2024.1/beta | 45 | 22 Nov 2024 | |
| 2024.1/edge | 50 | 09 Dec 2024 | |
| 2024.1/edge | 45 | 08 Oct 2024 | |
| 2023.2/stable | 3 | 06 Dec 2023 | |
| 2023.2/candidate | 17 | 25 Mar 2024 | |
| 2023.2/beta | 17 | 25 Mar 2024 | |
| 2023.2/edge | 17 | 23 Feb 2024 | |
| 2023.1/candidate | 8 | 12 Jan 2024 | |
| 2023.1/beta | 8 | 10 Jan 2024 | |
| 2023.1/edge | 8 | 12 Dec 2023 |
juju deploy keystone-ldap-k8s --channel edge
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
-
domain-name | string
Name of the keystone domain to configure; defaults to the deployed application name.
-
ldap-config-flags | string
The are ~50 LDAP configuration options supported by keystone. Use a json like string with double quotes and braces around all the options and single quotes around complex values. "{user_tree_dn: 'DC=dc1,DC=ad,DC=example,DC=com', user_allow_create: False, user_allow_delete: False}" See the README for more details.
-
tls-ca-ldap | string
This option controls which certificate (or a chain) will be used to connect to an ldap server(s) over TLS. Certificate contents should be either used directly or included via include-file:// An LDAP url should also be considered as ldaps and StartTLS are both valid methods of using TLS (see RFC 4513) with StartTLS using a non-ldaps url which, of course, still requires a CA certificate.