-
Notifications
You must be signed in to change notification settings - Fork 396
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
Checks.state argument is missing when trying to sign in inside an IFrame #541
Comments
Hi @GabrielMachado11 - thanks for raising this You're hitting a SameSite issue, because you're serving your site in an iframe. When the browser is redirected back to your site after logging in, it can't read your state cookies because they're in a 3rd party context (in an iframe). You should be able to workaround this by setting |
FYI it's the same change that we did in the express SDK here auth0/express-openid-connect#188 |
Hi @adamjmcgrath , thanks for your reply! No worries, i will wait for the changes |
I have the same issue without iframe. It seems that this error occurs when there is no required value in the cookie after the redirect. |
This is expected behaviour, you need to set a state check cookie by visiting |
hitting the same issue here... also using Nextjs and running inside an iFrame |
Same issue here testing a Nextjs app via Cypress locally. Works fine with remote URLs, but getting this error when running localhost:3000. |
@adamjmcgrath |
I'm experiencing exactly what @dqunbp described in a next.js app I'm working on. Most times the auth0 login works fine, however randomly we are getting the checks.state argument missing error on login. If the user attempts to log in again, it works. |
^^ I get the same too |
I read the FAQ and tried to reduce the size of the cookies, but that didn't solve the problem. |
Stuck on same issue |
I'm also getting stuck on the same issue. Are there any updates for this? |
Description
Reproduction
Environment
The text was updated successfully, but these errors were encountered: