[Bug]: Getting the keycloak screen (Account already exists) for a user who has successfully logged in via SAML in the past. - Githubissues

appsmithorg / appsmith

Platform to build admin panels, internal tools, and dashboards. Integrates with 25+ databases and any API.

https://www.appsmith.com

Apache License 2.0

32.52k stars 3.53k forks source link

[Bug]: Getting the keycloak screen (Account already exists) for a user who has successfully logged in via SAML in the past. #34219

Open nsarupr opened 1 month ago

nsarupr commented 1 month ago

SubTasks

Getting the following image when logging in via SAML

nsarupr commented 1 month ago

Scenarios tried for reproducing the issue.

Changing user email on Azure AD and trying to login. (test@appsmith.com -> test@appsmith0.com)
- Azure AD doesn't allow test@appsmith.com, but allow user to login with test@appsmith0.com and it created a new user account on Appsmith
Deleting the user (on Azure AD) and adding again and trying to login,
- Login was successful and the same workspace which was created when user was created in Appsmith for the first time.

At the moment, with the above scenarios, we were unable to reproduce this issue.