Repository navigation
Replies: 2 comments 3 replies
|
I have also posted this at https://keycloak.discourse.group/t/kc-17-x-x-how-to-access-admin-ui-from-port-forwarded-internal-url-prevent-redirect-from-internal-url-to-kc-hostname/14917 |
3 replies
|
Try hostname-admin-url instead |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Objective:
keycloak is deployed in kubernetes with proxy=edge with a hostname/KC_HOSTNAME=public.url. I want to restrict admin UI access by allowing it only from internal url by doing port-forwarding
kubectl port-forward svc/keycloak 9010:80
now http://localhost:9010/admin should work but https://public.url/admin shouldn't work (assuming that I blocked it using reverse proxy)
I have tried setting adminUrl using KC_HOSTNAME_ADMIN but it doesn't work.
Problem:
Currently port-forwarded local url http://localhost:9010 is working but it is redirecting me to KC_HOSTNAME :(
As far as I know same setup was working fine with keycloak <17
Environment variables:
KC_HOSTNAME=public.url
KC_PROXY=edge
Related information:
mentioned at https://www.keycloak.org/docs/latest/server_installation/
"If you do not want to expose the admin endpoints and console on the public domain use the property adminUrl to set a fixed URL for the admin console, which is different to the frontendUrl. It is also required to block access to /auth/admin externally"
All reactions