[bitnami/keycloak] Fix typos related to truststore (#10852)

* [bitnami/keycloak] Fix typos related to truststore

Signed-off-by: Kélian Saint-Bonnet <kelian.saintbonnet@gmail.com>

* Update README.md with readme-generator-for-helm

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>

Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com>
Co-authored-by: Jose Antonio Carmona <jcarmona@vmware.com>
This commit is contained in:
Kélian Saint-Bonnet
2022-06-24 16:32:26 +02:00
committed by GitHub
parent 59b6ffb0d2
commit fd2e02ba9c
2 changed files with 5 additions and 5 deletions

View File

@@ -26,4 +26,4 @@ name: keycloak
sources:
- https://github.com/bitnami/bitnami-docker-keycloak
- https://github.com/keycloak/keycloak
version: 9.3.0
version: 9.3.1

View File

@@ -111,7 +111,7 @@ auth:
## admin-password: myPasswordKey
## management-password: myManagementPasswordKey
## tls-keystore-password: myTlsKeystorePasswordKey
## tls-truestore-password: myTlsTruestorePasswordKey
## tls-truststore-password: myTlsTruststorePasswordKey
##
existingSecret: ""
## @param auth.existingSecretPerPassword Override `existingSecret` and other secret values
@@ -147,7 +147,7 @@ auth:
autoGenerated: false
## @param auth.tls.existingSecret Existing secret containing the TLS certificates per Keycloak replica
## Create this secret following the steps below:
## 1) Generate your trustore and keystore files (more info at https://www.keycloak.org/docs/latest/server_installation/#_setting_up_ssl)
## 1) Generate your truststore and keystore files (more info at https://www.keycloak.org/docs/latest/server_installation/#_setting_up_ssl)
## 2) Rename your truststore to `keycloak.truststore.jks`.
## 3) Rename your keystores to `keycloak-X.keystore.jks` where X is the ID of each Keycloak replica
## 4) Run the command below where SECRET_NAME is the name of the secret you want to create:
@@ -160,11 +160,11 @@ auth:
##
usePem: false
## @param auth.tls.truststoreFilename Truststore specific filename inside the existing secret
## Note: Setting up this value, you will use the same trustore file in all the replicas
## Note: Setting up this value, you will use the same truststore file in all the replicas
##
truststoreFilename: ""
## @param auth.tls.keystoreFilename Keystore specific filename inside the existing secret
## Note: Setting up this value, you will use the same trustore file in all the replicas
## Note: Setting up this value, you will use the same truststore file in all the replicas
##
keystoreFilename: ""
## @param auth.tls.jksSecret DEPRECATED. Use `auth.tls.existingSecret` instead