Re: [keycloak-user] Problem using Keycloak behind reverse proxy since 4.5.0.Final
Hello,
Beginning with 4.5.0, Keycloak Docker images use standalone-ha.xml by default instead of
standalone.xml. I think that might be the cause because you need to properly configure
http-listener (proxy-address-forwarding="true" etc.)
Cheers,
Dmitry Telegin
CTO, Acutus s.r.o.
Keycloak Consulting and Training
Pod lipami street 339/52, 130 00 Prague 3, Czech Republic
+42 (022) 888-30-71
E-mail: info(a)acutus.pro
On Mon, 2018-12-17 at 21:31 +0000, Munene Kiruja wrote:
I have keycloak in a bare metal kubernetes singe nod cluster. Its
installed using helm.
For https, we setup a reverse proxy in front of keycloak. First we use nginx with a lua
extension for oidc, and moved on to envoy proxy. Results are the same - works until
4.4.0.Final. Everything is working well as long as we use keycloak versions up to 4.4.0.
> From 4.5.0 and up, access https<server_ip:port>/auth/admin redirects to http
and fails.
I have spent much time going over the reverse proxy setup in the documentation (which
seems to have nothing new lately that should justify any changes since 4.4.0) and not made
any progress.
Can any one shed light on this darkness for us?
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user