KeyCloak login issue: user already exists

[ShellyXueHan]

Background:

After login with the identity provider, user sees a KeyCloak page with a message User with <email/username> already exists. How do you want to continue? from the application realm

Reference:

Steps to debug duplicated email:

• fist of all, try to clear cache and reopen browser to test a clean start
• check with realm admin on the login settings: Realm Settings -> Login tab -> Login with email If this field is set to true, no new accounts with duplicate email address can be created.
• check if any user account in the realm has the same email address as your currently account. This usually happens between two accounts from the same person (e.g.: IDIR and BCeID with the same email), or different accounts with empty email attributes.
• If that's the case, either enable Duplicate email setting, or update one of the accounts with another email address

Steps to debug duplicated username:

• fist of all, try to clear cache and reopen browser to test a clean start
• have you recently updated your IDIR/BCeID account? If so, please request for a KeyCloak user update at: https://github.com/BCDevOps/devops-requests
• if above does not apply, please contact RocketChat channel sso

[garywong-bc]

NOTE I now see a Configure -> Realm Settings -> Cache option that MDS could've tried prior to deleting the 2nd account (with the same email). The 1st account did NOT show up in the list of users but may have been in the cache. In the future, if this happens again we should try clearing the cache before making any config changes.

[aaabramov]

NOTE I now see a Configure -> Realm Settings -> Cache option that MDS could've tried prior to deleting the 2nd account (with the same email). The 1st account did NOT show up in the list of users but may have been in the cache. In the future, if this happens again we should try clearing the cache before making any config changes.

You saved me hours of investigation.. I was getting 409 for deleted user )

[zsamji]

closing as it is captured bcgov/sso-keycloak#70