-
Notifications
You must be signed in to change notification settings - Fork 42
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
Issue passing params to callback URL #44
Comments
Keycloak wants the request phase and the callback phase
So ultimately, the request phase I adapted the gem and ended up implementing something like this to allow the params to be passed through
|
I also encountered similar issues. when my |
@ushmakapure Thank you for your solution. It works. The only issue is if your params contains some url( |
I'm using omniauth-keycloak with devise in a rails + react project and I have keycloak omniauth hooked up successfully for regular login/signup. I'm trying to add it to the devise invitation flow and am running into an issue passing the
invitation_token
so it is accessible in the omniauth callback endpoint.I added the param into
authorize_options
and passed it as a hidden input in the form as per #24 but this doesn't seem to do anything to the callback request. I'm not sure if I'm misunderstanding the feature or if there is something wrong with the config.I also tried passing the param directly in the form action e.g.
action={'/auth/keycloak?invitation_token=${token}'}
but this causes anIncorrect redirect_uri
error in the callback phase, presumably due to theinvitation_token
in the query params. The keycloak integration redirect uri is set tohttp://localhost:3000/*
Relevant code:
The text was updated successfully, but these errors were encountered: