Repository navigation
Redirect URI #48745
Redirect URI
#48745
Replies: 1 comment 1 reply
|
The behavior you're seeing is by design — when a realm has its own A few things to check:
What exactly is the misbehavior? Is the redirect going to the wrong port, or is it returning an "Invalid redirect_uri" error? |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Using v26.x
KC_HOSTNAME is set to
<hostname>:<kc-hostname-port>/authRealm A has realmsettings/frontendUrl:
<hostname>:<kc-hostname-port>/authRealm B has realmsettings/frontendUrl:
<hostname>:<realm-b-port>/authWhen a user in realm A logs in a redirect sends the browser to:
<hostname>:<kc-hostname-port>/auth/realms/<realm-name>/protocol/openid-connect/auth...When a user in realm B logs in a redirect sends the browser to:
<hostname>:<realm-b-port>/auth/realms/<realm-name>/protocol/openid-connect/auth...I need to move all realms to redirect to:
<hostname>:<realm-b-port>/auth/realms/<realm-name>/protocol/openid-connect/auth...It seems that the kcadm.sh script is no longer able to set a realms frontendUrl attribute,
is there a setting that will override that attribute for all realms
UPDATE
If I completely remove Realm B realmsettings/frontendUrl, then login it now redirects to
<hostname>:<kc-hostname-port>/auth/realms/<realm-name>/protocol/openid-connect/auth...All reactions