UAE PASS Verification

UAE Pass Verification is a digital identity verification system that allows secure verification through a mobile application, offering a seamless and efficient way to verify user identities.

How to Setup

1 Go to Workspace > Workflows, and click on the flow created for UAE Pass Verification If you need understanding in creating a workflow, refer to the step-by-step guide here.

2 Hover over the plus (+) symbol and select Workflow. From the list, click UAE Pass Verification to add it.

3 Click on the newly added workflow, then select the General tab to customize your preferences.

Manage General

(*) Indicates an action to be mandatory.

Name	Description
Display Name*	Set a name to the workflow for easy identification.
Description	Summarize the purpose and functionality of this workflow module.
Enable	This toggle is enabled by default. When enabled, the particular workflow module begins its execution. Conversely, if disabled, the workflow module remains inactive and won't proceed.
Rule	This determines the criteria for triggering the particular workflow module. When the selected rule is evaluated, and is satisfied, the workflow proceeds as provided. if not, the workflow will not be executed. Note: If no rules are set, the workflow defaults to its standard action without any rule. For more information about the rules, refer here.

4 Then, click on the Configs tab to set the necessary configurations.

Manage Configs

Name	Description
Target App	Choose between the Staging and Production versions of the UAE PASS app. When opting for the Production app, ensure to configure the client ID and client secret in the workspace attributes, and create a base URL accordingly.
UAE PASS Claims	Claims specify the information that should appear in the generated response. Note that only the selected claims will appear in the final response. The claims for UAE PASS Verification are: uae_pass_verified: This denotes whether the UAE PASS verification is completed ("True" if completed, "False" if not). uae_pass_verified_at: Timestamp (in Unix epoch format) indicating when the UAE PASS was verified. access_token: Token issued by the UAE PASS server for authenticated access to resources. token_type: Type of token issued (e.g., Bearer). scope: Permissions granted to the access token (e.g., which resources can be accessed). mobile: The mobile number associated with UAE PASS. full_name_ar: Full name of the individual in Arabic. last_name_ar: Last name of the individual in Arabic. gender: The gender of the individual. full_name_en: Full name of the individual in English. last_name_en: Last name of the individual in English. uuid: Universally unique identifier (UUID) associated with the UAE PASS account. first_name_ar: First name of the individual in Arabic. first_name_en: First name of the individual in English. idn: Emirates ID number associated with the individual. nationality_ar: Nationality of the individual in Arabic. nationality_en: Nationality of the individual in English. user_type: Type of user account (e.g., individual). sub: Subject identifier for the user.

5 After you've configured everything needed, click on SAVE.

6 Proceed to attach the workflow to the relevant application for execution. Refer to the instructions on how to attach a workflow to an application here.

How it Works

note

The UAE PASS Verification has two types of verification methods,

• Web to App: This involves where the web application triggers the UAE PASS mobile app for identity verification. Any web-supported Verification Way and Result Notification Way can be used.

• App to App: This involves two mobile applications where one (ezto verify mobile) app triggers the UAE PASS app for identity verification. The Verification Way must be configured as Mobile, and the Result Notification Way should be set to Mobile SDK.

1 Launch Postman or your preferred API tool and execute the flow by configuring the suitable Method, URL, and Body settings. If you're seeking guidance on how to perform these actions, see here.

2 Upon initiating the API call, a verification request will be sent to your configured Verification Way settings.

3 Based on the request, execute the flow in an incognito browser and follow the prompts to complete the verification process.

Web to App

• You will be redirected to the UAE PASS portal. Please enter your login credentials and proceed.

• After you log in to the UAE PASS portal, a number (such as 85) will be displayed.

• You will receive a notification on your UAE PASS mobile app. Open the notification to view the request details.

• If the request details match your actions, from the set of numbers, select the number that matches the one shown on the login portal and click on the Confirm button.

• You will be prompted to enter your UAE PASS PIN to verify your identity.

• The verification will be completed if the PIN is correct.

Here is a sample flow:

App to App

• Begin by scanning the QR code with the ezto verify mobile app.

This depends on what you have configured for the mobile notification way, i.e, QR code or Push integration. To know the difference between QR code or Push, refer here.

• After scanning the QR code with the ezto verify app, you will be asked to grant permission to open the UAE PASS app. You will be asked to provide permission only the first time.

• The UAE PASS app will open, displaying the request details. If the request details match your actions, click on the Confirm button.

• You will be prompted to enter your UAE PASS PIN to verify your identity.

• You will then be redirected to the ezto verify mobile app once the verification is complete.

Here is a sample flow:

4 The response can differ depending on the chosen Verification Way and Notification Way configurations. To know more, see here.

5 Here is a sample response for UAE PASS Verification:

{
  "uae_pass_verified": "true",
  "uae_pass_verified_at": "1722496607",
  "sub": "47149b03-0f68-4ea5-aa3b-bade40f047fb",
  "request_id": "ccf1d5e0-dc0a-4fb1-a5df-a5f68494db53",
  "gender": "male",
  "workflow": "verification",
  "mobile": "9198246756399",
  "token_type": "Bearer",
  "uuid": "47149b03-0f68-4ea5-aa3b-bade40f047fb",
  "access_token": "9f166b42-f4f1-34f1-8c5e-7685440402c0",
  "user_type": "SOP1",
  "first_name_en": "Mark",
  "user_id": "mark@gmail.com",
  "scope": "urn:uae:digitalid:profile:general urn:uae:digitalid:profile:general:profileType urn:uae:digitalid:profile:general:unifiedId",
  "full_name_en": "Mark",
  "last_name_en": "G",
  "expires_in": "3600",
  "email": "mark@gmail.com"
}