Repository navigation
Incorrect redirect_uri #25684
|
I am attempting to upgrade to the latest Keycloak (v23.0.3) from an older working v20.0.2 instance. Simply using the same redirect_uri setting for a client doesn't work anymore. The client is running on Wildly v26.1.3 with a patched Elytron. Is there some trick to configuring validRedirectUri in Keycloak or is this combination of Elytron and Keycloak a no-go? The error in the Wildfly log when I attempt to login: I've tried adding a bunch of valid redirect URIs and even tried a single asterisk, which apparently doesn't mean anything goes:
I guess I'll stick to the old version for now, but eventually I need to patch and move forward. What gives? Is 23.0.3 busted? Maybe the existence of URL parameters in the return_uri is no longer tolerated by Keycloak? The login returns back to the app with "Forbidden" displayed (Wildfly/Elytron generated HTML) and the URL has the original page params intact plus additional Keycloak params: My understanding is the recent best practice is for page URL parameters to be bundled up into the |
Replies: 3 comments 14 replies
|
Related:
There is a lot of activity related to |
|
@slominskir Yes, there have been several security issues so now the comparison is more strict for sure. But for understanding this better, can you please paste the exact redirectUri that is in the browser if possible? (Just copy the redirect query param as it's in the browser). |
|
@slominskir I have done a little test with 23.0.3 and using the url you set in point 3: Are you sure the openidc URL is that one? The error is displayed at that point, right? |
Yep! It's the iss, if you see the two redirect_uri are just different because of the iss param. Go to your client and in the
Advancedtab setExclude Issuer From Authentication Responseto ON.This problem is not related to teh changes in the redirect_uri validation but with the new iss parameter introduced by the spec. Your client does not remove it from the URI.