Just tested that @home, and actually multiple configuration additions are needed:
1/ Run the keycloak container with env -e PROXY_ADDRESS_FORWARDING=true
as explained in the docs, this is required in a proxy way of accessing to keycloak:
docker run -it --rm -p 8087:8080 --name keycloak -e PROXY_ADDRESS_FORWARDING=true jboss/keycloak:latest
Also explained in this SO question
2/ Change the web-context inside keycloak's configuration file $JBOSS_HOME/standalone/configuration/standalone.xml
Default keycloak configuration points to auth
<web-context>auth</web-context>
Then you could change it to keycloak/auth
<web-context>keycloak/auth</web-context>
If you need to automate this for docker, just create a new keycloak image :
FROM jboss/keycloak:latest
USER jboss
RUN sed -i -e 's/<web-context>auth</web-context>/<web-context>keycloak/auth</web-context>/' $JBOSS_HOME/standalone/configuration/standalone.xml
3/ Add some proxy information to nginx configuration (mostly for http / https handling)
location /keycloak {
proxy_pass http://example.com:8087;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
If you are proxying requests from nginx to keycloak on same server, I recommend using proxy_pass http://localhost:8087;
, and if not try to use a private network to avoid proxying through external web requests.
Hope this helps
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…