UAE PASS
  • UAE PASS
  • Overview
  • Getting Onboarded with UAE PASS
    • Onboarding Process for UAE PASS Service Providers
      • Initiation Phase
      • Development Phase
      • Assessment Phase
      • Go live Phase
  • Quick Start Guide - UAE PASS Staging Environment
    • User Account Types
    • Create Staging UAE PASS Account
    • Upgrade Staging UAE PASS Account
    • Testing Credentials for POC
    • Conduct a POC with UAE PASS Authentication
  • Feature Guides
    • Authentication
      • Web Integration
        • Introduction
        • Pre-Requisites
        • Endpoints
        • 1. Authorization Code
        • 2. Access Token
        • 3. User Information
        • 4. Logout
        • Login Button
        • Authentication Postman Walkthrough
      • Mobile Integration
        • Introduction
        • Pre-Requisites
        • Requirements
        • Guide
          • SDK
          • API
        • SDK Integration
      • Token Validation API
        • Introduction
        • Pre-Requistes
        • Endpoints
        • Integration Steps
          • 1. Verify access token API using Basic Authentication
          • 2. Obtaining Authenticated User Information from the Access Token
        • Validation Decisions
      • User Linking
        • Automatic Linking
        • Manual Linking
        • Corporate Account
    • Digital Signature
      • Digital Signature (Single Document)
        • Signing Guide
          • Endpoints
          • Document Signing Steps
            • 1. Token
            • 2. Create Signer Process
            • 3. Sign Document
            • 4. Obtaining Document
            • 5. LTV Configuration
              • Integration Web Services
              • Postman Collection for LTV
            • 6. Deleting Document
          • Document Signature verification Process
          • Postman Collection for Digital Signature
            • Digital Signature Postman Walkthrough
        • Verification API Integration
          • Web Service Details
          • Postman Collection for Signature Verification API
      • Digital Signature (Multiple Document)
        • Signing Guide
          • Endpoints
          • Document Signing Steps
            • 1. Token
            • 2.Create Documents
            • 3. Create Signer Process
            • 4. Sign Document
            • 5. Obtaining Document
            • 6. LTV Configuration
              • Integration Web Services
              • Postman Collection for LTV
            • 7. Deleting Document
          • Document Signature verification Process
          • Postman Collection for Multiple Document Signing.
    • e-Seal
      • Introduction
      • DESC Process for Dubai Entities
        • Process overview
        • Detailed DESC process description
      • ICA Process for Non-Dubai Entities
        • Onboarding Process
        • Obtaining Credentials and Certificates
      • Integration Web Service
        • PAdES eSeal Signing
        • CAdES eSeal Signing
        • eSeal verification
        • eSeal error codes
      • Postman Collection
    • Hash Signing
      • Introduction
      • Hash Signing (Single Document)
        • Hash Signing (Java SDK Set Up)
          • Quick Setup
          • Hash Signing Process
            • 1. Start the Process
            • 2. Initiate Signing Process
            • 3. Sign PDF Document
          • Endpoints
          • Postman Collection
          • Utility Files
      • Bulk Hash Signing (Multiple Documents)
        • Quick Setup
        • Hash Signing Process
          • 1. Start Signing Process
          • 2. Initiate Signing Process
          • 3. Sign PDF Document
        • Endpoints
        • Postman Collection
  • Web Registration
    • Introduction
    • Steps to create account
    • Endpoints
      • 1. Access Code
      • 2. Access Token
      • 3. User Information
  • Facial Biometric Transactions Confirmation
    • Web Integration
      • Endpoints
      • Integration Steps
        • Obtain Authorization Code
        • Obtain Access Token
        • Obtain User Info
        • Log out User
    • Mobile Integration
      • Mobile Integration Guidelines
  • Guidelines
    • Use-Case Guidelines
      • Standard Authentication Scenarios for Service Provider Use Cases
      • Standard Digital Signature Scenarios for Service Provider Use Cases
      • Standard Implementation Guidelines
    • Design Guidelines
      • UAEPASS Button Guideline
      • Text Message Guidelines
  • Resources
    • Attributes List
    • Sample Apps
    • Staging Apps
    • Assets
  • FAQ
    • Common Integration Issues
  • Versioning
Powered by GitBook
On this page

Was this helpful?

  1. Feature Guides
  2. Authentication
  3. User Linking

Manual Linking

PreviousAutomatic LinkingNextCorporate Account

Last updated 3 months ago

Was this helpful?

If user is having existing native credentials in service provider portal, but no matching attributes (Email or Emirates ID), service provider should provide an option for the user to manually link both the accounts.

Service Providers delegate the authentication processes to UAEPASS. By doing so, Service Providers should be able to identify UAEPASS users and link them to their internal user repository through key attributes shared by UAEPASS. Every profile in UAEPASS has a unique identifier (UUID) that could be used as a key attribute to link users in Service Providers repository, and Emirates ID when dealing with Verified users (SOP2 and SOP3).

Note: At anytime, users on UAE PASS can update their email and mobile number after verifying that the user is in possession of the email address or mobile number.

As such, if Service Providers depend on mobile number or email address from UAEPASS to link users, this link becomes orphaned once the user change the values on UAEPASS. SP will end up creating multiple accounts for the same user.

Local Account
User Profile
Action

Manual Linking (One time activity)

This is user initiated to link their existing account in Service Provider with UAEPASS

SOP 1, 2, 3

If no unique key attribute (SPUUID, EID, Email, Mobile). Ask the user if local account exists in SP

  • If yes, user enters local SP username/password and link accounts

  • If no, the SP creates new user profile by popylating UAEPass data in SP registration form.

Page Layout

Yes: When clicked, the user will be redirected to the local service provider login page for both UAEPASS and local profile will be linked and merged.

No: When clicked, the user will be redirected to the usual registration page where he/she will provide essential information (SP can pull KYC data from UAEPASS instead of asking the user to typre them, like Name, DOB, etc.)

If User clicks Yes:

The user Needs to enter the logon credentials in order to link the local account with UAE PASS account.

If User clicks No:

The SP will show the local registration form and populate UAE PASS data such as (EID, Name, Email, Mobile) and it should not be editable. The rest of the fields can be manually entered by the user.

Note: User should not be able to Edit UAE PASS data in the Registration Form nor in User Profile.

Figure 7: Account Linking