[bitnami/keycloak] KEYCLOAK_HOSTNAME present even if KEYCLOAK_PROXY_HEADERS is set #30182
Assignees
Labels
keycloak
solved
stale
15 days without activity
tech-issues
The user has a technical issue about an application
triage
Triage is needed
Comments
RDemarneffe
added
the
tech-issues
javsalgar
changed the title
|
Hi! Thank you so much for reporting. I will forward it to the team but as it is not a critical feature we cannot guarantee an ETA. If you want to speed up the process, you can submit a PR and the team will check it. |
RDemarneffe
added a commit
to RDemarneffe/charts
that referenced
this issue
Nov 8, 2024
4 tasks
RDemarneffe
added a commit
to RDemarneffe/charts
that referenced
this issue
Nov 8, 2024
Signed-off-by: Renaud Demarneffe <[email protected]>
4 tasks
|
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
|
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Name and Version
bitnami/keycloak:24.0.4
What architecture are you using?
None
What steps will reproduce the bug?
Into the Helm chart of Keycloak, the configuration variable
KEYCLOAK_HOSTNAMEis always set once the ingress is enabled.However, as stated into the Keycloak startup log, when this variable is set, the content of the variable
KEYCLOAK_PROXY_HEADERSis never taken into account.Are you using any custom parameters or values?
No response
What is the expected behavior?
When the helm
proxyHeadersvariable is set, theKEYCLOAK_HOSTNAMEinto the config map should not be set.What do you see instead?
The
KEYCLOAK_HOSTNAMEis always set when ingress is enabled.Additional information
No response
The text was updated successfully, but these errors were encountered: