Overview:
Currently, Any user user initiating a first time SSO login using an identifier that already exists in the custodian org - causes an auto migration of the account from custodian to the state tenant since it can cause erroneously migration. If an identifier erroneous migration to avoid it user's acknowledgment is required.
If the user is found to match an account in the custodian org when the user tries to login via SSO for the first time, the user should be prompted about the existence of the duplicate account , and asked whether the account belongs to them.
If the user stakes claim to the account, they have to prove ownership of the existing account (in custodian) by providing the password to the account. If a valid password is provided, the account in the custodian org is migrated to the state tenant. The SSO details sent by the state will apply to the new account for the user.
If the user refutes ownership of the existing account, they are provided with a new account on the state tenant as per the standard SSO workflow. The identifier is assigned to the new account in the state tenant. The old account in custodian that existed is stripped of the identifier and made inactive.
Problem statement:
Account auto-merge workflow should be handled in portal securely. Currently only the existing user's are migrated
Solutions:
...
Step 1: In the screen, the user will enter Phone/Email and UserName with which he has signed up in Sunbird. User can retry if the UserName doesn't match only one time. If he couldn't find his account after 2 failed attempts, then he should be redirected to the Login page with proper massage. If the user entered details yields matched accounts(can contain more than one identifier like phone, email, prev used phone, prev used email) user will be redirected to next step.
Step 2: Here user can choose to which contact channel he wants his OTP to be sent to. The list will contain all matched accounts contact channel(phone, email, prevEmail, prevPhone). OTP should be sent to contact channel that the user enters. If the OTP was successfully sent user will be redirected to the next step. If the user refreshes the page, then we need to redirect him to the first step.
Step 3: Here user can verify the OTP that has been sent to contact type of his choosing. If he fails to validate the account even after the second attempt he should be sent to the login page. If verification is successful, then the user will be redirected to the next step. If the user refreshes the page, then we need to redirect him to the first step.
Step 4: Here he can enter new password and confirm it to recover the account. If the password reset successful user will be redirected login page with succus message. If the user refreshes the page, then we need to redirect him to the first step.
Drawbacks: While SSO user is prompted to update email/Phone if not present already.
Step 2: An OTP is generated and the user is allowed to enter received OTP.
Step 3: For new users if email id is already found in dupe check show user a confirmation popup to initiate account migrate. If user deny to merge deactivate the non state user account and create new account.If user
allows to merge goto step 4
Step 4: User is allowed to enter the password if the password is correct initiate migration of account else allow user to re enter password.
Step 5: Users re enters password. If password is correct initiate account migration else create new account for user.