Prior to installation, the system must be bootstrapped with certain authorization server credentials and secrets. There are a few alternative ways to perform this task.
Authorization Server Credentials
The authorization server credentials can be provided to the system in the following ways:
...
Necessary authorization server credentials for Secret or Helm, respectively, are listed in the table. These credentials need to be provided before installation can complete:
Secret Parameter | Helm Parameter | Description |
---|---|---|
managementApiUsername | authorizationServer.management-api.username | HTTP Basic Authentication Username |
managementApiPassword | authorizationServer.management-api.password | HTTP Basic Authentication Password |
jwtKeystore | authorizationServer.jwt.keystore | Secret Parameter - File path of a keystore encoded in Base64 format Helm Parameter - File path of a keystore |
jwtKeyId | authorizationServer.jwt.key-id | Alias of the RSA private/public key pair used for JWT |
jwtKeyPassword | authorizationServer.jwt.key-password | Password of the RSA private/public key pair used for JWT |
jwtKeystorePassword | authorizationServer.jwt.keystore-password | Password of the keystore |
Kubernetes Secret
Credentials can be written into a Secret object, which must be named authorization-server-secrets prior to installation.
Expand | ||
---|---|---|
| ||
|
Helm Values
Expand | ||
---|---|---|
| ||
|
...
Code Block |
---|
base64 -i <keystore file path> -o <B64 keystore file name>.txt |
Info |
The keystore file will be found at '/opt/mz/persistent/keys/keystore.jks' after running the helm install command. |
Random
If neither Secret nor Helm values are used to provide managementApiPassword credentials, the required values are automatically populated with random data. For users with access rights, the randomized credentials can be retrieved by doing:
...