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 :

...

1. verify the message on cancel and merge screen - Rajeev discussed same will be changed by PM.
2. is username from state and keycloack auth token is diffent what error message and screen should be shown -  Need to show error message in error message screen. 
3. check if we can use the manual merge screens with username field already having value and user cannot edit it.

Catch in the process- ?

how mobile will login to system in case of google and normal sign as now we are passing the keyclaock token in query and allow user new state user to login to system.

Issues with mobile team-

1. mobile team will send client_id ='android' when the sso flow starts and portal will capture and this parameter will be send to all flow.
2. On keycloak sign in -
   1. mobile team will capture the code
   (
   1. param given after successful
   login via
   1. sign from keycloack
   )
   1. and store it
   and
   1. in memory (check ) 
   2. if migrate
   success
   1. is successful mobile will generate new session from code and login user else close the flow (check if we get update values of not) new user should be logged in as a state user  .
   for google sign everything will be send as a paramerter
3. On google sign in -
   1. Mobile closes Webview
   2. google page opens in custom tab (redirect url is passed with query params, which includes encrypted data )
   3. On successful login, the encrypted data along with generated AccessToken/RefreshToken is appended to redirect invalid URL to be captured by mobile
   4. mobile continues flow by opening another Webview with predefined URL along with data captured from step 'b'.
   5. poratl redirects to successful/erroneous redirect and mobile closes the webview.

UI Screens

Verify user via email or phone

...