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.

Solution 1:

...

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

Conclusions after first 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

Things to discuss

1) Sending username phone number/ email address as the query parameter

...