You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Incosistency between redirect_uri at different API endpoints
#42647
I mean, sure, i can provide a redirect_uri myself, but i have 3 separate applications running, one for the frontend, one for Keycloak and one for the backend. The backend currently doesn't need to know where exactly the frontend is running, because Keycloak's frontend handles the redirects itself, and i would really like to leave it at that.
I am aware that i could get the client name out of the token and then get the actual client with its base url from Keycloak and use that. But why must i jump through those hoops to emulate the default behavior of PUT /admin/realms/{realm}/users/{user-id}/send-verify-email on this other API endpoint? Am i missing something?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I stumbled over the fact, that the optional API parameter
redirect_uriis handled very differently when not provided.At the PUT /admin/realms/{realm}/users/{user-id}/send-verify-email endpoint the default for the redirect is the account client.
At the PUT /admin/realms/{realm}/users/{user-id}/execute-actions-email endpoint the default for the redirect is, that there will be no link back to click after actions have completed.
What's the rational between those completely different behaviors? And how can i make PUT /admin/realms/{realm}/users/{user-id}/execute-actions-email to behave in the same way as PUT /admin/realms/{realm}/users/{user-id}/execute-actions-email, to use the Client base url?
I mean, sure, i can provide a
redirect_urimyself, but i have 3 separate applications running, one for the frontend, one for Keycloak and one for the backend. The backend currently doesn't need to know where exactly the frontend is running, because Keycloak's frontend handles the redirects itself, and i would really like to leave it at that.I am aware that i could get the client name out of the token and then get the actual client with its base url from Keycloak and use that. But why must i jump through those hoops to emulate the default behavior of PUT /admin/realms/{realm}/users/{user-id}/send-verify-email on this other API endpoint? Am i missing something?
All reactions