-
Notifications
You must be signed in to change notification settings - Fork 968
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
bug: OIDC account linking causes error "session is not resumable" #1786
Comments
This is covered and passing in the e2e test suite so it might be something else. |
It very likely might be. I need more time and I will come back with more debug info. |
I think we can close this one. We probably found a bug and I think it is related to unreleased code. We will test it on the branch with #1527 and apply fix if needed (our current implementation is bit different so it may not be needed). |
aeneasr
added a commit
that referenced
this issue
Jan 10, 2022
Closes #2016 Closes #1786 Closes ory-corp/cloud#1786 Closes #2108
7 tasks
aeneasr
added a commit
that referenced
this issue
Jan 10, 2022
Closes #2016 Closes #1786 Closes ory-corp/cloud#1786 Closes #2108
aeneasr
added a commit
that referenced
this issue
Jan 10, 2022
…2131) Closes #2016 Closes #1786 Closes ory-corp/cloud#1786 Closes #2108
peturgeorgievv
pushed a commit
to senteca/kratos-fork
that referenced
this issue
Jun 30, 2023
…ry#2131) Closes ory#2016 Closes ory#1786 Closes ory-corp/cloud#1786 Closes ory#2108
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
So there seems to be some issue with OIDC settings flow. When trying to link any OIDC account kratos generates error:
It seems that when posting a settings form to
/self-service/settings
it successfully reads and continues with the continuity session. Now browser is redirected to an OIDC provider (say google for example) and there it continues with the flow after which it is redirected back to/self-service/methods/oidc/callback/google
where it tries again to resume this session and it fails since the continuity session was destroyed when handling a POST to/self-service/settings
. At least that is what I think it is happening and looking at the logs from Kratos.Reproducing the bug
Steps to reproduce the behavior:
/error
pageServer logs
Expected behavior
User can successfully link an existing account to OIDC provider.
Environment
The text was updated successfully, but these errors were encountered: