Mock MDS : The mock MDS is a utility that simulates the MDS by returning synthetic biometrics during biometric capture. This can be used for testing the functionality of the registration client when the actual Biometric devices and corresponding MDS are not available.
Note : Before running the mock MDS, it is required to register the mock MDS as a biometric partner. This is not discussed within the scope of this document.
2. TPM Utility
3. Syncbyte MDS Client & document.
Latest SyncbyteMosipRDServiceSetup 0.0.9.5_2.0.0.5_Production attached.
SyncbyteMosipRDServiceSetup 0.0.9.5.exe (Version 2.0.0.5) 0---- with IRIS fix
Notes #
a) Image Blurness ratio introduced for Iris Scanner in config.properties
Usage Values
-------------
irisBlurThresholdMin=0.10
irisBlurThresholdMax=0.70
MosipClient.exe MosipClient_0.0.9.5_1.0.0.0_x86_Release.rar (Version 3.0.0.0)
Notes #
a) Client application can be used to test the 0.9.5 and 1.0.0 MOSIP Specs
Language change:
In Syncbyte software change the language to French as mentioned below.
Go to “C:\Program Files\Syncbyte Innovations Private Limited\SyncbyteMosipRDService\source” path and edit config.properties file and change the value to “fr” for key “language”. (ex: language=fr)
4. Print Listener
To generate PDF file and print, extract the zip file and use java command to run Print-Listener-1.1.5.2.jar file and this should be running in a machine where printer is connected.
Note: There is a separate print listener for on-prem and on-cloud environment.
5. Registration Client Url. (Note: You need to connect to Wireguard to access this url)
On-Cloud: https://regclient.togo-pilot.mosip.net
On-Prem : https://regclient.mosip.anid.gouv.tg
6. Operator/Supervisor Training document.
Both French & English version of document available.
7. Registering and Onboarding Machines, Operator and Supervisor
Both French & English version of document available.
8. Reporting Dashboard SQLs
9. ID Authentication Demo Application - This application is used to demonstrate the authentication services.
NPrime FingerPrint L1 Device SDK
Iritech MDS
ID Auth Demo App
Steps to configure NPrime FP L1 Device
Download attached SDK Zip file (SM-91MAuthSBISetup-v0.9.5.1.5.zip)
Extract the zip file
To install, run setup.exe in Adminstrator mode
While installing keep all options with default values
Copy attached config.properties and replace with existing one in C:\NPrime\Auth\SM-91M\config
Connect the device
Find AuthTestFp.html in the SDK zip extracted folder and open in the browser
Select the Port number(on which device is connected) from the dropdown
Verify all three options(Discover Device, Device Info and Capture Fingerprint)
From Discover Device output note down deviceId value
Steps to run ID Auth Demo App
Download attached ID Auth Zip file (Auth Demo UI.zip)
Extract the zip file
Open application.properties in an editor
Look for 'ida.request.captureFinger.deviceId' property and update the value with 'deviceId' value which got from 'Discover Device'
Look for 'ida.captureRequest.uri' property and make sure the port number in the value is correct on which L1 device is configured
Now to launch the application, execute run.bat script file.
10. Tech5 Windows BioSDK - Following are the steps to enable local deduplication and quality check at RegClient
Download the attached native-togo zip file
Extract the zip file in the required place
Copy the folder path where the zip file is extracted
Go to System Environment Variables setting application
In the System Variables section add new variable called FACE_SDK_BIN_ROOT and value is native-togo folder path
Append the same native-togo folder path in Path variable also
Copy config.properties and iris_sdk.lic files from the extracted native-togo folder
And paste in the RegClient application root folder
To enable this feature at Registration Client application, following properties should be enabled with flag 'Y' in registration-default.properties file which is present in mosip-config repository in GitHub.
mosip.registration.mds.deduplication.enable.flag
And additionally following properties need to be updated with Vendor(who is going to support Local Deduplication) specific SDK class path. Here are the properties specific to Tech5 vendor
mosip.biometric.sdk.provider.finger.classname=ai.tech5.client.ClientSDK
mosip.biometric.sdk.provider.iris.classname=ai.tech5.client.ClientSDK
Note: Vendor specific(Tech5) SDK is integration with latest regclient zip. Please download the latest one to avail this feature.
Now system is ready to perform local deduplication and biometrics quality check
Pre-requisite
The operator/supervisor should have been onboarded
'default' role is not mapped in the user object of the operator/supervisor in keycloack
The operator/supervisor's RID is present in user attribute list in keycloak as below
Updating the login authentication mode
By default, the login authentication mode is password-based. In order to change the authentication mode, it is necessary to update the database directly. At the time of writing this procedure, we observe that there are no APIs available to update the authentication mode without touching the database directly.
The following are the authentication modes available
Supported Authentication Methods:
"OTP"
"IRIS"
"FACE"
"FINGERPRINT"
"PWD"
Supported Authentication Methods:
"OTP"
"IRIS"
"FACE"
"FINGERPRINT"
"PWD"
In order to change the authentication mode, login to the PostgreSQL database, and connect to mosip_master schema using any of the supported database client utility such as pgAdmin and run the following update queries
Disable password based authentication for operators and supervisors
-- To disable password authentication --
UPDATE app_authentication_method
SET is_active=false, upd_dtimes=now()
WHERE role_code in ('REGISTRATION_OFFICER','REGISTRATION_SUPERVISOR')
AND auth_method_code='PWD'
AND process_id IN ('login_auth', 'packet_auth', 'eod_auth', 'exception_auth'); |
Save or commit the DB changes.
Enable a Biometric Fingerprint authentication mode for operators and supervisors
-- To enable finger print authentication --
UPDATE app_authentication_method
SET is_active=true, upd_dtimes=now()
WHERE role_code in ('REGISTRATION_OFFICER','REGISTRATION_SUPERVISOR')
AND auth_method_code='FINGERPRINT'
AND process_id IN ('login_auth', 'packet_auth', 'eod_auth', 'exception_auth'); |
Save or commit the DB changes.
Note 1 : In-order to enable other biometric authentication modality such IRIS or Face, replace the auth_method_code with “IRIS” or “FACE” respectively.
Note 2 : In-order to enable biometric authentication for operator only and not the supervisor, give the appropriate role_code in the update query.
Once the above queries are successfully executed, perform the following operations on the registration client where the operators need to login using their biometrics
From the home screen of the registration client, perform sync operation.
After the successful completion of the sync operation, logout of the registration client and enter the user name of the operator.
You would see the following screen displaying the biometric mode of login (in this case fingerprint)
.png?version=1&modificationDate=1657191895684&cacheVersion=1&api=v2 "Togo MOSIP Pilot > Tools & Utilities and Documents > image (3).png")
Note : To enable biometric Login for operator only, simply change the role_code='REGISTRATION_OFFICER' in the above SQL query.
You may place your left 4-finger to authenticate and login into the registration client.
