User Linking
UAEPASS User Linking Flow
Use Cases
We are detailing here few use cases and SP can handle accordingly:
Use Case 1
User logged in using his UAEPASS Account and the user is having an existing account in SP application, then allow the user to connect its SP user account with UAEPASS account {Integrating parties should support two modes as applicable.}
Automatic Linking
In case Automatic Accounts Linking is adopted "this is applicable if the relying party maintains the IDNnumber of the Emirates ID (or any other common attributes) for local users and in this case the link happens depending on the IDN."
Other attributes like date of birth, passport number or any shared attribute between the User Profile in UAEPASS and Relying Party are also recommended to be used to uniquely identify user if applicable.
Note: For linking, it is recommended to use “uuid” attribute returned by UAEPASS for user linking purposes for subsequent visits.
Manual Linking
In case Manual Linking is adopted, the user should be challenged by the Relying Party application with his Relying Party's account username and password (or any other authentication mechanism) and on successful authentication, the linking can be achieved by storing the linking attributes (e.g.uuid, idnetc.) at Relying Party side. This is one time activity and should be done only on first linking attempt.
Note: For linking, it is recommended to use “uuid” attribute returned by UAEPASS for user linking purposes for subsequent visits.
Use Case 2
User has logged in using his UAEPASS Account and the user is non-existing user in Relying Party application, then allow the user to register and create account using the User Information retrieved from UAEPASS.
Auto Populate Form
User is creating an account with entity and he has not logged in using UAEPASS, entity should give the end user the option to auto populate entity User Form using the UAEPASS Authentication Service.
Register using UAE PASS option
UAEPASS can be used to populate Local User Registration Form for Relying Party Registration.
Use Case 3
On Successful authentication at UAEPASS, the control is sent back to SP irrespective of user type. The SP should handle the authorization or flow at their end as per the user types and their business.
SOP1 : In case of SOP1, UAEPASS will not return the Emirates ID number attribute as the user has still not verified his/her emirates ID at this stage. SP should handle such case by showing an appropriate error message to SOP1 Users.
Last updated
