-
-
Notifications
You must be signed in to change notification settings - Fork 351
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
Upgrading to alerta 9.0.0 breaks keycloak integration regardless of /auth
path
#1835
Comments
@hyberdk Are you sure? This commit should have been in the version we are using but our installation still broke? |
not 100% :-) |
Hi. |
@maksimse Yes, that bug is still not fixed. As a workaround we switched to the OIDC configuration:
|
@bo0ts , thank you very much! It works. |
Issue Summary
After upgrading to alerta 9.0.0 login via keycloak is not working anymore. We run Keycloak 19 on Wildfly (which still has the
/auth
path which has only been removed on the quarkus distribution).If we set the keycloak url to
https://keycloak.intern
the API will fail to start.If we set the keycloak url to
https://keycloak.intern/auth
the API will start but the login button will redirect tohttps://keycloak.intern/auth/auth
and login will fail.We worked around the issue by specifying the generic openid auth provider.
Environment
The text was updated successfully, but these errors were encountered: