Overview:

Currently, Any 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 it can cause 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.

...

Account auto-merge workflow should be handled in the portal front end and portal backend. An auto migration of the account from custodian to the state tenant it can cause erroneous migration to avoid its user's acknowledgment is required.

...

Approach :

Image RemovedImage Added

...

Step 5: Users re-enter the password. If the password is correct initiate account migration else create a new account for the user.

Solution 2

Initiate a manual merge flow process for auto-merge as well.

Conclusions after

...

design discussion

1. ask PM to verify the message on cancel and merge screen
2. Check if same design works fine with the mobile team as well.
3. encrypt the user's identifier (email or phone number) after it verifies the otp  and send it to keycloack and receive the same back
4. before calling migrate api check if same user is merging or not to do this take token from step 3 and token generated after sign in should have same email id.
5. send complete of state user token to keycloack server

Question to PM?

1. verify the message on cancel and merge screen
2. is username from state and keycloack auth token is dirrent what error message and screen should be shown 
3. check if we can use the manual merge screens with username field already having value and user cannot edit it.Send state token along with email/Phone number encrypted in redirectUri while opening keycloack page.
4. Mobile team should append client_id='andriod'.
5. Before calling migrate API portal should perform the following checks
   - Decrypt the encrypted data to get state token, user email 
   - Check if state token is valid using echo API
   - Check if state token is not expired.
   - Verify the access token
   - Check if email Id from encrypted data and the access token is same.
6. Only after all checks in step 3 are passed migrate API can be called. 
7. Once migration is done user will be notified via email from backend.
8. Mobile related changes - 
   User will be logged as a nonstate user after the user enters password or Gmail.
   Mobile needs to detect by reading the query parameter if auto-merge is in progress or not.
   If auto-merge is in progress mobile will call to portal sending encrypted data and access token to migrate the user.
   
   
   

Open questions for the mobile team? 

Draw.io flow chart link to edit - Untitled Diagram (2).drawio

UI Screens

Verify user via email or phone

...