• CONTAINERS , LINUX
Keycloak and oauth2-proxy
Keycloak and oauth2-proxy
Using the Keycloak Docker image:
To run Keycloak:
podman run -e KEYCLOAK_USER=admin -e KEYCLOAK_PASSWORD=admin -p 8443:8443 --volume /home/bward/keycloak/certs:/etc/x509/https --volume /home/bward/keycloak/data:/opt/jboss/keycloak/standalone/data jboss/keycloak
To increase the debug/trace loglevel, use KEYCLOAK_LOGLEVEL=ALL
podman run -e KEYCLOAK_LOGLEVEL=ALL -e KEYCLOAK_USER=admin -e KEYCLOAK_PASSWORD=admin -p 8443:8443 --volume /home/bward/keycloak/certs:/etc/x509/https --volume /home/bward/keycloak/data:/opt/jboss/keycloak/standalone/data jboss/keycloak
To run the oauth2-proxy
podman run --volume /home/bward/oauth-proxy-my-app/oauth2-proxy.cfg:/etc/oauth2-proxy.cfg --volume /home/bward/oauth-proxy-my-app/certs:/etc/x509 -p 4180:4180 oauth2-proxy/oauth2-proxy:latest --config=/etc/oauth2-proxy.cfg
Oauth2-proxy has very little information in logging. To debug it, I built and ran
podman run --security-opt seccomp=unconfined --volume /home/bward/oauth-proxy-my-app/oauth2-proxy.cfg:/etc/oauth2-proxy.cfg --volume /home/bward/oauth-proxy-my-app/certs:/etc/x509 -p 4180:4180 -p 4080:4080 oauth2-proxy-debug:latest --config=/etc/oauth2-proxy.cfg
Debugging golang:
Docs
TODO:
-
Go back and ensure all SSL configs on both keycloak, oauth2-proxy, and app
-
fix backchannel logout by setting trust store — why does it need this here if the rest works fine?? probably because the server is now sending a request, instead of just responses during the login sequence