Typebot
Log in

Share feedback, ideas and get community help

Updated 6 months ago

Removing an orphaned Oauth Account

At a glance

A community member had a client added to a workspace, but the client's Azure AD account was deleted due to an issue with Office 365. Now, when the client tries to log in, they receive the message "To confirm your identity, sign in with the same account you used originally." Other community members suggest that the issue may be because the client's email address is the same, but the GUID (Globally Unique Identifier) is different. The solution proposed is to delete the user from the Account table, which should allow the client to log in with any provider.

LLindaRobertsCS
I had a client added into a workspace, and their account on the azureAD side was deleted due to an issue over at office 365 and we used the same email address. but now when they try to login they get this "To confirm your identity, sign in with the same account you used originally." anyone have any ideas on what's going on here?
B
L
7 comments
BBaptiste
So now they are trying to login by email instead of Azure AD?
LLindaRobertsCS
no The user originally logged with Azure AD but we had to delete thier account cause it was setup wrong and re-created it. It used the same Email but the GUID was different
LLindaRobertsCS
sorry about the late response on this
LLindaRobertsCS
they are still using AzureAD to login but i think cause its the same email but different GUID its not liking something.
BBaptiste
You should delete the user from the Account table
BBaptiste
Then he'll be able to log in with any provider.
LLindaRobertsCS
ok thank you
Add a reply
Sign up and join the conversation on Discord