#409 improve docs for KeycloakUser password generation
This commit is contained in:
parent
8f25167b8e
commit
1f72559dfb
1 changed files with 7 additions and 2 deletions
|
@ -23,6 +23,9 @@ spec:
|
||||||
email: "user@example.com"
|
email: "user@example.com"
|
||||||
enabled: True
|
enabled: True
|
||||||
emailVerified: False
|
emailVerified: False
|
||||||
|
credentials:
|
||||||
|
- type: "password"
|
||||||
|
value: "12345"
|
||||||
realmRoles:
|
realmRoles:
|
||||||
- "offline_access"
|
- "offline_access"
|
||||||
clientRoles:
|
clientRoles:
|
||||||
|
@ -70,8 +73,10 @@ image:images/realm_user.png[]
|
||||||
|
|
||||||
.Results
|
.Results
|
||||||
|
|
||||||
After a user is created, the Operator creates a Secret containing the both username and password using the
|
After a user is created, the Operator creates a Secret using the
|
||||||
following naming pattern: `credential-<realm name>-<username>-<namespace>`. Here's an example:
|
following naming pattern: `credential-<realm name>-<username>-<namespace>` , containing the username and, if it has been specified in the credentials attribute, the password. If no password is specified Keycloak will create a random one, but it won't be populated in this Secret.
|
||||||
|
|
||||||
|
Here's an example:
|
||||||
|
|
||||||
.`KeycloakUser` Secret
|
.`KeycloakUser` Secret
|
||||||
```yaml
|
```yaml
|
||||||
|
|
Loading…
Reference in a new issue