Hello,
I am working on a Keycloak POC and I have successfully created an image and deployed it to an Azure Kubernetes Service cluster.
When I access the app I am prompted to create the admin user (as expected).
I can access Keycloak using localhost:8443 and create the admin account.
I get a 404 error though on the file step1.html when trying to access the admin console.
This is the path that generates the 404 error: https://localhost:8443/realms/master/protocol/openid-connect/3p-cookies/step1.html?version=56pvt
i have same issue, and already tried to fix for 3 full days.
Maybe situation is little different, i run my admin on a internal different domain…
Admin is working (also step1.html) when fully running on main public domain, but when using the internal domain, everything ok except step1 en step2 gives 404…
When i manually change it to the public domain the html is there.
So somehow only these html files don’t work on the internal domain how come
I had the same issue. I had an old version of keycloak and wanted to update it to 19.x. My setup needs to be deployed under the path /auth. So I used KC_HOSTNAME_PATH=auth.
But apparently that messes up the admin panel. The admin panel doesn’t take this KC_HOSTNAME_PATH into account apparently (my guess). In order to make it work I had to redirect / and /auth to the root of keycloak. See my ingress config: