User xxx already exists with provider openid #9563
Unanswered
xinguaws
asked this question in
Troubleshooting
Replies: 1 comment 1 reply
-
Yes this is expected now. There is no cross-over allowed now. The database entries have to be manually updated. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What happened?
I switched from openid to saml around v0.7.8 or 0.7.9, users can log in normally after the switch, and user's mongo record attribute simply updated from provider: "openid" to provider: "saml", however, after upgraded to latest v0.8.0-rc3, I have users reported they can't login with error message:
User xxx already exists with provider openid
, I had to run a mongo query to manually updated the record, is this expected or a bug?Version Information
v0.8.0-rc3
Steps to Reproduce
already mentioned in the issue description
What browsers are you seeing the problem on?
No response
Relevant log output
Screenshots
No response
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions