-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
After 7.3.0 authentication for web mvc client against keycloak ends in endless redirect #174
Comments
This error is thrown by Keycloak. Have you changed one of:
The last two points lead to a new authorization-code callback that could possibly not be allowed in Keycloak. But according to the little log you join, it seems that you have an issue with the authorization-code itself. Please attach more Keycloak logs. Please also add your security conf ( What is the version of Keycloak you are using? Can you setup a minimal reproducer? I don't have this kind of error with my OAuth2 clients authenticating users on Keycloak |
here i've added a minimal projekt |
@yennor thank you for the reproducer, it is of great help for investigations. What I spotted so far is that inside This is a regression I'll fix (haven't found why yet and have limited time today, but will do soon). |
@yennor I published a This issue was specific to synchronized apps (servlets). |
works like a charm. thanks a lot :-) |
Describe the bug
I use a webmvc client authenticating against keycloak.
It works perfectly up to and with version
7.2.0
.From
7.3.0
on it doesn't work anymore.The client always throws a
Keycloak shows me a
I think I had a similar error in the past once. As far as I remember the problem was using different redirect_uri for the code and the token or something like that (long time ago).
I've tried to look through the changes from
7.2.0
to7.3.0
but I don't understand them 100%. But something changed with the redirect_uri, as far as i can see.But the whole thing ends in an endless redirect from keycloak, to localhost, back to keycloak, ...
config looks like:
The text was updated successfully, but these errors were encountered: