Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current Restore this Version View Version History

« Previous Version 18 Next »

Overview

The Community Registration Client is a mobile and tablet application that serves as a portable version of the existing desktop Registration Client. It has been developed to support accessibility on all Android devices. The introduction of the Community Registration Client came about in order to meet the mobility requirements of countries adopting MOSIP.

The primary objective of the mobile version is to facilitate the registration process for residents, specifically those who are unable to physically visit registration centres and also serve remote locations where setting up a Registration centres aren’t feasible. To address this challenge, the Community Registration Client was created, enabling operators and supervisors to easily reach remote areas and maximise resident registrations across the country.

How to install Android Reg Client:

  1. Download and install the APK on Android tablet.

  2. Once Android Reg Client 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:

    1. Go to resources/ machine and click on “Create machine”

    2. Add a new machine and enter the machine details:

      1. Add the specs as “Mobile”

      2. Map it to a center and zone

      3. machine spec ID as “Mobile”

      4. Enter Device name

      5. Enter Public Key

      6. Enter Sign Public Key

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

    4. Create the operator’s user account in KeyCloak and set the password and assign the role as “Default”, “REGISTRATION_OFFICER”, “Registration Operator”, “REGISTRATION_SUPERVISOR”,

    5. Login into Admin Portal to perform the following to add the user:

      1. After login into admin portal, go to user zone mapping and add the zone for the user and activate the zone

      2. Go to user center mapping and add the center for the user and activate the center

      3. Note: The user should be mapped to the same Zone and Center to which the device was mapped to.

Assumptions: The tablet is a biometric enabled tablet with SBI already setup, if people are evaluating this application on non biometric tablet. comment

Features:

Below are the key features available in the first developer release of Android Reg Client:

  1. Operator/Supervisor Login (offline and online): The Operators can login using their credentials in offline as well as in online mode and proceed with their transactions. For the offline login to work, the Operator must have logged in at-least once and performed sync over network.

  2. Multi language support: Multiple languages are supported on the Android Reg client for content display and data entry.

    1. Display Language: Display Language is the language in which the UI elements like labels and headings are rendered. Android Registration Client enables the Operators to choose the preferred language in which they want the UI to be displayed. This option is available on the login screen. The presently supported display languages are Arabic, French, English, Hindi, Kannada and Tamil.

A new language can be added by following the below steps:

  1. Additional languages can be added by adding localisation files in this folder. Flutter docs (https://docs.flutter.dev/ui/accessibility-and-localization/internationalization ) 

lib/l10n

ii. The languages that are rendered on the UI will be based on the country configuration (after master data sync). The default display language is English. The other languages will be available in the UI after master data sync.

  1. Data Entry Language: Data Entry Language is the language in which the Operator collects the data and the data is stored in that language in the server. The data collected by Operator during registration process can be chosen based on the preferred language of the applicant. This option is available after initiating a new registration. The data entry language is controlled by UI Spec and can be changed by modifying the same.

  2. Auto-Sync/ manual sync: On launching Android Reg Client and logging in for the first time, the system automatically syncs the following data:

    1. Configuration sync: Sync of properties which drives in deciding the ARC UI functionality. For example: Invalid login attempts, idle timeout, thresholds, etc.

    2. Masterdata sync : As a part of this sync, supporting information like Dynamic fields data, templates, locations, screen authorization, blocklisted words, etc. are pulled in.

    3. UserDetails sync: userID, along with their status is synced. Only the user details belonging to machine mapped center will be synced.

    4. Certificate sync: Certificates used to validate the server signatures, device CA certificates, public key (specific to a center and machine, also called as policy key) used to encrypt the registration packet will be synced.

This feature also enables the Operator to perform manual sync as required using the “Synchronize Data” option.

  1. New Registrations: Operators can register a resident using “New Registration” feature. The new registration flow can be configured using UI spec. Below are the data that needs to be captured to register an applicant:

    1. Consent: New registration of an applicant starts by seeking consent to the terms and conditions mentioned on the consent screen that explicitly asks the applicant to allow MOSIP to store and utilise their PII (Personally Identifiable Information).

    2. Demographics: Once the consent is duly accepted, the Operator will enter the demographic data of the applicant. Demographic details could include details like Name, Gender, DOB, Residential Address, etc.).

    3. Documents: Once the demographic screen is duly filled, the operator can choose the document type, enter the reference and upload the supporting documents shared by the applicant. Supporting documents could include as Proof of Address, Proof of Identity, Proof of Birth etc. based on the norms defined by the country.

    4. Biometrics: Once the documents are duly uploaded, the Operator will capture the biometrics of the Applicant. The biometrics captured are as follows:

      1. Finger print

      2. Iris scan

      3. Photo

      4. Exception photo

The capture of biometrics is governed by the country, i.e. capture of each modality (fingerprint, iris or face) can be controlled by the country using the global configuration. When the operator clicks on the Capture button, the control goes to biometric SBI application where the biometrics are captured. Once the biometrics are captured, the data and the control goes back to the Android Reg Client. To capture the biometrics of the resident, the quality of the captured image should be more than the threshold configured by the country. The biometrics can be captured for a configured number of times in order to cross the quality threshold set limit. In a scenario where none of the captured images cross the threshold, the one with best quality score will be stored.

If the resident has a biometric exception (i.e. resident is missing a finger/eye or quality of finger/iris is very poor) the Operator can mark that particular biometrics as exception but the Operator has to capture the resident's exception photo.

e. Preview section: The Operator can preview the data (demographic data, documents uploaded and biometrics captured) along with entered along with the Applicant to ensure that the data entered is correct. If any of the data is incorrect, the Operator can enter the correct data by going back to the respective section to correct it. If the data is correct, they can proceed to the next step which is to authenticate himself.

f. Operator authentication: Once the Operator and applicant has checked that the data is duly filled, the Operator has to authenticate himself using his credentials. Once the authentication is successful, the packets get uploaded to the server on availability of network.

g. Packet sync: Once the applicant’s registration form is duly filled and the Operator has authenticated himself, a packet sync will have to be performed post which the packet will be ready to be uploaded (the uploaded packet status will be synced from server).

h. Packet Upload: Once the packet sync is successful, on availability of internet connection, the system will upload the packet to the server. On unavailability of network, the system will attempt to upload the packet to the server whenever connectivity is established.

i. Acknowledgment section: Once the new registration process is completed, an acknowledgment receipt is generated. The details displayed on the acknowledgment receipt will contain the captured demographic data in the selected language, photograph of the resident and ranking of each finger from 1 to 10 (1 being the finger with the best quality). This receipt is print friendly and can be used for printing using any printer.


  1. Operator onboarding: The operator, in order to login to Android Registration Client, will have to onboard himself. This functionality is available on first time online login only. The Operator will have to onboard himself by capturing his fingerprints, thumb print, iris, and face. Once these are captured, the Operator can start registering residents and start using other services.

  2. Update Operator onboarding: The Operators can also update their biometrics. In this scenario, the Operator will have to capture all their biometrics. On doing this, the

  3. Dashboard: The Operator can access the dashboard where he can view the statistics of packets.