From ab31c94a6e8b7a38c762a3ef79017fa668d4fb2a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20P=C3=A9g=C3=A9?= Date: Mon, 18 Oct 2021 12:28:50 +0200 Subject: [PATCH] [bitnami/keycloak] Add the solution for #6940 in docs - SSL Offload (#7838) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Add the solution for #6940 in docs * Update README.md Co-authored-by: Carlos Rodríguez Hernández --- bitnami/keycloak/README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/bitnami/keycloak/README.md b/bitnami/keycloak/README.md index 841d70dfb2..b3d79757dd 100644 --- a/bitnami/keycloak/README.md +++ b/bitnami/keycloak/README.md @@ -377,6 +377,16 @@ To enable Ingress integration, set `ingress.enabled` to `true`. The `ingress.hos The chart also facilitates the creation of TLS secrets for use with the Ingress controller, with different options for certificate management. [Learn more about TLS secrets](https://docs.bitnami.com/kubernetes/apps/keycloak/administration/enable-tls-ingress/). +### Use with ingress offloading SSL + +If your ingress controller has the SSL Termination, you can add the following env vars in `extraEnvVars` +```yaml +- name: KEYCLOAK_PROXY_ADDRESS_FORWARDING + value: "true" +- name: KEYCLOAK_FRONTEND_URL + value: "https://keycloak.xxx" +``` + ### Manage secrets and passwords This chart provides several ways to manage passwords: