-
Notifications
You must be signed in to change notification settings - Fork 79
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
Error after Keycloak login "No matching state found in storage" #1501
Comments
@debegr92 - We're seeing the same thing with our project, however it works on a local development machine - but not when we deploy to a test server. Did you have any luck finding a solution? |
Okay, here is what I did @zach-betz-hln
Same result. First login shows "no matching state". Logout and login again then works (the default router shows nothing for my callback route, but I can see the home button and my token). I am using a working Keycloak cloud instance and try to implement the user login on my local machine. So therefore I added the 127.0.0.1 as valid redirect URL in Keycloak. |
@debegr92 - Interesting. Now I am wondering about the config of your Keycloak cloud instance. One thing you could try with the sample repo is running it once with default config, then again pointed to your Keycloak cloud instance, and compare the responses in the DevTools Network tab. Do your usual login/logout flow then compare the responses in each run for relevant differences. |
I try to use react-oidc-context in a small example project. Most of it based on the code of this README.md.
It seems like the onSigninCallback is not working properly and I need a second login to get the correct state, token and user info.
This is the behavior
keycloakConfig.tsx
main.tsx
App.tsx
The text was updated successfully, but these errors were encountered: