-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Keycloak Quarkus distribution #1709
Comments
I think we can remove auth. Problem is that we break others like kas installer. Adding additional flag to skip it sounds like hack. @rkpattnaik780 do you have some ideas |
I think we should go with additional flag to skip it as removing it can break stuffs.
|
Hi @andreaTP |
@rkpattnaik780 sorry for the confusion, please use the version from the branch |
Description
Version:
0.48.0
rohas login
command already works against new versions of Keycloak, but the token refresh fails because it injects/auth
into the URL path (which is no anymore mandatory since Quarkus distribution).For example, after running a login like:
We receive the error:
Steps to reproduce
rhoas login --api-gateway http://localhost:8081 --auth-url http://localhost:8083/realms/demo-apicurio --client-id apicurio-cli
Expected vs actual behaviour
The CLI should respect the URL without injecting
/auth
.Workaround
Is currently possible to workaround this issue by setting the retro-compatibility option:
KC_HTTP_RELATIVE_PATH: /auth
https://github.com/andreaTP/srs-fleet-manager/blob/b2fe84f373c33ff32f5ecf7b4f42b31fcc48b3fc/dist/k8s-dev/keycloak.yaml#L47-L48
The text was updated successfully, but these errors were encountered: