You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The support for setting proxy modes is deprecated and will be removed in a future Keycloak release. Consider configuring accepted reverse proxy headers instead as described in the chapter above. For migration instructions consult the Upgrading Guide.
Run Docker container with KEYCLOAK_PROXY=edge for example.
See the following warning in the container logs:
WARN [org.keycloak.quarkus.runtime.cli.Picocli] (main) The following used options or option values are DEPRECATED and will be removed in a future release:
- proxy: Use proxy-headers.
What is the feature you are proposing to solve the problem?
This Docker image should probably swap the KEYCLOAK_PROXY environment variable for a new one called KEYCLOAK_PROXY_HEADERS, mapping to the proxy-headers setting in Keycloak.
Thanks for taking the time to create this ticket and report this change. I just created a ticket on our side to take care of the changes. However, I can't provide you with an ETA on when this change will be ready. We will notify you when having more information.
Name and Version
bitnami/keycloak:24
What is the problem this feature will solve?
Keycloak 24 introduces changes when it comes to proxy configuration.
See in particular:
--proxy-headers
option keycloak/keycloak#25178It looks like
--proxy-headers
is the only option supported now, isn't it?How to reproduce:
KEYCLOAK_PROXY=edge
for example.What is the feature you are proposing to solve the problem?
This Docker image should probably swap the
KEYCLOAK_PROXY
environment variable for a new one calledKEYCLOAK_PROXY_HEADERS
, mapping to theproxy-headers
setting in Keycloak.Note: this change will affect the Keycloak chart at https://github.com/bitnami/charts/tree/main/bitnami/keycloak.
What alternatives have you considered?
Not really an "alternative", but in the meantime, I used
KEYCLOAK_EXTRA_ARGS: --proxy-headers xforwarded
to run Keycloak 24 (on Kubernetes).The text was updated successfully, but these errors were encountered: