End User Guide

Login using OTPLogin using OTPThis user guide is designed to provide assistance to Operators and Supervisors in successfully installing, running, and registering applicants to obtain their Unique Identification Numbers (UIN) on tablet devices.

Prerequisites

• Reliable and consistent Internet connectivity.

• Tablets running Android version 10 to 13.

• Tablets with a minimum of 4 GB RAM.

• The tablets need to be capable of capturing fingerprints, iris, and face (photo) biometrics. Additionally, they should also have the ability to scan documents. However, if the tablets do not support these capabilities, MOCK SBI can be used as an alternative.

How to install Android Registration Client (ARC)

1. Download and install the APK on Android tablet.

2. Once ARC is installed, long press on the logo to copy the machine details.

3. On the Admin Portal, using admin credentials, login and perform the following to add the device:

   • Go to Resources/Machine and click on Create machine

   • Add a new machine and enter the machine details:

     • Add the specs as Mobile

     • Map it to a Zone and Center

     • Add the Machine spec ID as Mobile

     • Enter Device name

     • Enter Public Key

     • Enter Sign Public Key

   • Create the role Default in KeyCloak with all the other roles.

   • Create the Operator’s user account in KeyCloak set the password and assign the role as Default, REGISTRATION_OFFICER, Registration Operator, REGISTRATION_SUPERVISOR

   • Login into Admin Portal to perform the following and add the user:

     • After login into the Admin Portal, go to User Zone Mapping and add the zone for the user and activate it.

     • Go to User Center Mapping and add the center for the user and activate it.

1. The user should relaunch the ARC and log in using their valid credentials. Additionally, the operator has the option to select their preferred display language.

Upon successful login, the user will be directed to the Home page, which includes the following options:

• New Registration

• Operational Tasks

• Dashboard

• Settings (Future scope)

New Registration

To begin the Registration process, the Operator is required to follow the steps outlined below.

1. Click on New Registration card.

2. Select the language to be used for data entry, which will be used to collect the resident's information. There will be a default language for data entry.

3. Choose the language in which the notification will be sent to the resident. Click Submit to proceed.

1. The operator will be redirected to the Consent page, where the resident must agree to the terms and conditions to proceed.

2. After accepting consent, the Operator will need to fill out the demographic data of the resident, including their name, age, date of birth, and address. Once all mandatory fields are completed, the Continue button will be enabled.

1. Upon clicking the Continue button, the Operator will be navigated to the Document upload page where they will need to:

   • Select the type of document (e.g. proof of identity, proof of address) from the drop-down menu.

   • Enter the Reference Number of the document.

1. Upload the document by clicking on the Scan button to open the camera. The Operator can take a picture of the document and then choose from the following actions:

   • Cancel: Clicking on the "Cross" icon will remove the captured image and return the Operator to the previous screen.

   • Crop: The Operator can drag from the four corners of the captured image to crop it as needed.

   • Save: Clicking on the "Save" button will save the captured image and return the Operator to the previous Document Upload page.

   • Retake: Clicking on the "Retake" button will remove the captured image, reopen the camera, and allow the Operator to take a new photo.

1. After ensuring all required information has been accurately entered into the Document Upload screen, the Operator can proceed by clicking on the Continue button to access the Biometric Capture page. Here, the Operator can capture the biometric data of the Resident, including a face photo, fingerprint, and iris scan.

Face photo capture process

• To capture the face photo, the Operator should click on the Scan button to activate the camera and take a picture.

• The image quality will be displayed on the screen and must meet a certain threshold to be considered acceptable.

• The Operator has three attempts to capture the biometric image.

• It is important to note that no exceptions can be made for the face photo biometric capture process.

Biometric Data Capture Process:

• To capture biometric data, the Operator should click on the Scan button.

• This will allow the Operator to capture the biometric information.

• Once the data is captured, the image quality will be displayed on the screen and must meet the acceptable threshold limit.

Note: Three attempts are provided to capture the biometric data.

Fingerprint Capture Process:

If a thumb is missing or experiencing difficulties that prevent its fingerprint from being captured, the Operator is authorized to indicate an exception. To mark an exception, the operator must select the affected thumb and specify the type of exception as either Temporary or Permanent. Additionally, the operator may include any relevant additional comments.

Iris Scanning Process:

• To initiate the Iris scan, the Operator is required to click on the Scan button.

• This action will allow the Operator to capture the Iris image.

• Once the Iris has been successfully captured, the quality of the image will be displayed on the screen.

• The quality score needs to meet the established threshold limit.

• The Operator has three opportunities to capture the biometric data.

If one or both of the Irises are not detected or encounter issues that prevent successful capture, the Operator has the option to mark an exception. To do so, the Operator must identify the specific Iris that is problematic and indicate the type of exception- either Temporary or Permanent. Additionally, the Operator may provide any relevant comments.

1. After all the biometric data has been properly captured or any exceptions have been noted, the Continue button will be activated. The Operator can then proceed by clicking on the Continue button, which will redirect them to the Preview page. The Preview page will display the following information:

• Application ID

• Timestamp of Registration

• Demographic data collected

• Documents submitted

• Biometric data recorded

From the Preview page, the Operator can navigate back to previous screens to make any necessary adjustments to the entered or captured data. Once the Operator has verified the accuracy of the entered data, they can proceed by clicking on the Continue button, which will direct them to the Operator Authentication page.

1. On the Operator Authentication page, operators are required to input their credentials (username and password) that were used during the login process.

Upon successful verification of the credentials, the packet will be uploaded to the server and the operator will be redirected to the Acknowledgment screen. This screen includes the following information:

• Application ID

• Timestamp of Registration

• Demographic data captured

• Documents uploaded

• Biometric data captured

• Print option

• QR code for the Application ID

• Option to initiate a new registration process.

Pending Approval:

Upon successful verification of the credentials, the acknowledgment will be displayed, and the Application will be moved to the “Pending Approval” section. This feature will only be available for the User who has a Supervisor’s role assigned to him.

Once the packet is created by the Operator, as an additional check, the Supervisor will have to go through each application to make sure the details filled are coherent.

Step 1: The user goes to the “Pending Approval” section from the Operational Tasks section. The user will be taken to the page where they can see the list of all the Applications created by the Operator. All of these Applications will be “Pending”.

Step 2: The Supervisor then clicks on the Application ID one by one. At this stage, the Supervisor can either Approve the Application or he can Reject it. If the Supervisor decides to reject it, they also will have to mandatorily mention the reason for rejection.

Step 3: Once the Application has been Approved or Rejected, the Supervisor will have to authenticate himself by clicking on the “Submit” button and thereby entering their Username and Password. The User can also bulk submit the Applications. The only pre-requisite is that the packet has to be in Approved or Rejected status (pending Applications cannot be submitted for uploading). Once they have successfully authenticated, the Application will be removed from the “Pending Approval” section and will be moved to the “Manage Application” Section.

Step 4: Once the Application is either Approved or Rejected by the Supervisor and is submitted, those packets can be uploaded to the server from the “Manage Application” section or can be exported to their local device storage.

Manual Application upload/export

Once the Application is either Approved or Rejected by the Supervisor, those packets can be uploaded to the server from the “Manage Application” section.

Step 1: The user selects the packets they want to upload (bulk upload can also be done). Once selected, the user clicks on the “Upload” button, after which the packet syncs and gets uploaded if there is internet connectivity.

In case of a lack of internet connectivity, the User can also export the packet to their local device storage. They can also bulk export the packets by choosing the Applications and clicking on the Export button.

On choosing to upload, the packet is uploaded to the Registration Processor. Once the packet has been successfully processed, a unique identification number (UIN) is generated.

1. Print- The operator can click on this option to obtain a physical copy of the acknowledgment.

2. New Registration- The operator can initiate another registration by clicking on this option.

In summary, the user (Operator/ Supervisor) can follow the aforementioned steps to register an individual by capturing demographic data, documents, and biometric data to generate their UIN.

Operator Onboarding: To begin the Onboarding process, the Operator is required to follow the steps outlined below. The operator, to log in to the Android Registration Client, will have to onboard himself. This functionality will be available on first-time online login only.

a. On logging in for the first time, the Operator will be taken to the screen where they will have the following two options:

1. Get onboard: This flow is present for the system to verify the Operator’s biometrics with their registered biometrics. This is to enable local deduplication. To get onboarded the operator must not be assigned "default" role.

2. Skip to home: This flow is to dodge “Operator’s Onboarding”. If the user selects this, they will be taken to the “Homepage” after which the user can get started with Resident registration. One of the prerequisites of this flow is to have the “Default” role mapped to the center.

1. Steps to Onboard Operator’s Biometrics:

   a. The user will be taken to the Biometrics Capture Homepage where he will be able to see all the below biometrics:

   1. Face capture

   2. Iris capture

   3. Left-hand finger capture

   4. Right-hand finger capture

   5. Thumb capture

b. The user will then have to capture all the above-listed biometrics one by one. c. Steps to capture the biometrics are given here. d. Once all the biometrics are duly captured, the below acknowledgment message will be displayed on the screen.

1. Dashboard: The Operator can access the dashboard where he can view the following:

   1. Packets created: This will show the total number of packets created from the time the Android Registration Client was installed.

   2. Packets Synced: This will show the total number of packets synced from the time the Android Registration Client was installed.

   3. Packets Uploaded: This will show the total number of packets uploaded from the time the Android Registration Client was installed.

   4. User details:

      1. User ID: This will show the list of User IDs of the Users mapped to the device.

      2. Username: This will show the list of usernames of the Users mapped to the device.

      3. Status: This will show the status of Users mapped to the device. This can take values such as onboarded, active, inactive, etc.

In summary, the aforementioned steps can be followed by the user (Operator/ Supervisor) to onboard themselves, update their biometrics, or view the Dashboard.

Update UIN

In a scenario where the Resident wants to update their data, they can do so by letting the Operator know their UIN along with the data that needs to be updated. Residents can update their demographic details, documents, and biometrics using this feature.

Step 1: Go to “Update UIN” from the Homepage

Step 2: Enter the UIN of the Resident and choose the data to be updated.

Step 3: Enter the data that the Resident wants to update. It could demographic data, documents, and biometrics.

Step 4: Once all the required data is filled, the User will be taken to the Preview screen (data can still be modified) and then to the Acknowledgment screen (data cannot be updated hereafter).

Step 5: The user will then have to authenticate himself using his Username and Password. Once the authentication is successful, the packet will be uploaded to the server.

1. Logout: Using this feature, once the user is done with their registration and other activities, they can logout. If no background tasks are running, the user will be immediately logged out. If there are tasks (like sync) running in the background, the user will be notified about the same. From here if the User wants to cancel the logout, the background activities will keep running where whereas if the user chooses to logout, they will be logged out and the background activities will be terminated.

Update operators biometrics

This feature will be used by the operators to update their biometrics. They can follow the below steps for the same:

a. The user will be taken to the Biometrics Capture Homepage where he will be able to see all the below biometrics:

1. Face capture

2. Iris capture

3. Left-hand finger capture

4. Right-hand finger capture

5. Thumb capture

b. The user will then have to capture all the above-listed biometrics one by one.

c. Steps to capture the biometrics are given here.

d. Once all the biometrics are duly captured, the below acknowledgment message will be displayed on the screen.

Handles Feature Authentication:

Assumption: The Handles feature is enabled, and the email ID is designated as a Handle during registration.

Scenarios: A resident attempts to log into the Resident Portal using their Handle (i.e., email ID).

Step 1: Open the Resident Portal and navigate to "UIN Services."

Step 2: The resident will be taken to the eSignet login page.

Step 3: Choose the option to “Login using OTP”

Step 4: Enter the attributes marked as Handle (email ID in this case) and click on “Get OTP”. OTP will be sent to registered email ID and/or mobile number

Step 5: Enter the OTP received over the registered email ID and/or mobile number

Step 6: Select/De-select the Claims based on preference.

And click on the “Allow” button.

Step 7: You have now successfully authenticated and logged into Resident Portal via eSignet using handles (email ID in this case).

Forgot Password

In a scenario where the Operator has forgotten their password, this feature enables the Operator to set a new password to be able to login using the new password and continue with registration tasks.

Step 1: Run Android Registration Client on your system to land on the Login page.

Step 2: Click on Forgot Password option, You will then be redirected to the keycloak Login page.

Step 3: Click on Forgot Password option on the Keycloak login page.

Step 4: Enter your Keycloak Username and click on Submit.

Step 5: You will then receive an email over registered email Id to reset the password. This email contains a link to set a new password.

Step 6: On clicking on the link to set a new password, you (Operator) will be taken to the keycloak page where you can enter the new password. On successfully entering the password twice, the password will be changed. This password can now be used to log into Android Registration Client (when in online mode). In offline mode, the User will still be able to login using the older password until the system goes online and syncs atleast once after resetting the password.

AID QR code scan

This feature enables the Operator to scan the QR code of the AID (Application ID) QR code generated during pre-registration. On successful scan, the Operator will be able to fetch the pre-registration data and pre-fill the registration form with the available data.

Step 1: Log into Android Registration Client, start new registration to land onto the "Demographic Details" Page.

Step 2: On the "Demographic Details" page, click on the scan button next to "Fetch Data" option. On clicking on the scan button, camera will open up.

Step 3: You can then scan the QR code generated during Applicantʼs pre-registration.

Step 4: On scanning, the Application ID field will be pre-filled with the AID. Along with that, other details, as filled during pre-registration, like Name, age, gender, documents etc. will also be auto filled.

The pre-filled data can also be edited based on the your (Operator) or Residentʼs preference.

Lost UIN:

In a scenario where a Resident has lost their UIN, they can go to a registration center to retrieve their lost UIN. Below are the steps for the same:

Step 1: You (Operator) have to Launch Android Registration Client and login using valid credentials.

Step 2: Click on "Lost UIN" option on the home page.

Step 3: You (Operator) will then have to select the Data Entry Language and the Preferred Language of Communication.

Step 4 You can then ask and inform the Residents about the Consent and click on "Informed" button.

Step 5 You can fill the demographic details of the Resident. This is an optional step.

Step 6 You will have to capture all the biometrics of the Resident. This is a mandatory step.

Step 7: Once you (Operator) have duly captured the biometrics of the Resident, you can then proceed by clicking on the Continue button, which will redirect you to the Preview page. The Preview page will display the following information:

• Application ID

• Timestamp of Registration

• Demographic data collected (if any) Biometric data recorded

From the Preview page, you (Operator) have the the ability to navigate back to previous screens in order to make any necessary adjustments to the entered or captured data. Once you have verified the accuracy of the entered data, you can proceed by clicking on the Continue button, which will direct them to the Operator Authentication page.

Step 8: On the Operator Authentication page, you (operator) are required to input your credentials (username and password) that were used during the login process.

Step 9: Once that is done successfully, the packet is uploaded to the server and you (operator) will be redirected to the Acknowledgment screen. This screen includes the following information:

• Application ID

• Timestamp of Registration

• Demographic data captured (if any)

• Biometric data captured

• Print option

• QR code for the Application ID

• Option to go to the Homepage

Reset password:

In a scenario where the you (Operator) wish to set a new password, you can set a new password using this feature post which you will be able to login using the new password and continue with registration tasks.

Step 1: Launch Android Registration Client and login using valid credentials.

Step 2: Click on the "Profile" Icon on the Home page

Step 3: On the Profile page, click on the "Reset Password" option.

Step 4: On clicking on the "Reset Password" option, You will be redirected to the Keycloak Login page.

Step 5: You can then login using Keycloak credentials.

Step 6: Once you have logged in, you will be taken to the Password section where you can set a New Password.

Once the password is reset, new password can be used to log into Android Registration Client (when in online mode).

Note: In offline mode, you will still be able to login using the older password until the system goes online and syncs atleast once after resetting the password.