Starting with Keycloak 17 for the Quarkus distribution:
The new distribution introduces a number of breaking changes,
including:
Configuring Keycloak has significantly changed
Quarkus is not an application server, but rather a framework to build applications
/auth removed from the default context path
Custom providers are packaged and deployed differently
Because of the third bullet point you are getting
But I can’t access auth page https://:8443/auth/. There is always
“Page not found” error.
You can get around this issue with one of two solutions:
-
Use the previous endpoints, but now removing
/auth
from them or; -
as pointed on in the documentation:
By default, the new Quarkus distribution removes /auth from the
context-path. To re-introduce the /auth use the http-relative-path
build option. For example: bin/kc.[sh|bat] start-dev –http-relative-path /auth