Content Comparison

...

• 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

11. Enabling Operator Login with Biometric : -

Pre-requisite

1. The operator/supervisor should have been onboarded

2. 'default' role is not mapped in the user object of the operator/supervisor in keycloack

3. The operator/supervisor's RID is present in user attribute ist list in keycloak as below

Updating the login authentication mode

...

In order to change the authentication mode, login to the PostgreSQL database, the and connect to mosip_master schema using any of the supported database client utility such as pgAdmin and run the following update queries

• Execute below query to disable Disable password based authentication for all the Operators. operators and supervisors

  Code Block
  language sql
  -- 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.

• Execute below query to enable a different Enable a Biometric Fingerprint authentication mode such as fingerprint authentication for all the Operators.for operators and supervisors

  Code Block
  language sql
  -- 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 clients 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 may would see the login following screen displaying the biometric mode of login (in this case fingerprint login)

...

Note : To enable biometric Login for Supervisoroperator only, simply change the role_code='REGISTRATION_SUPERVISOROFFICER' in the above SQL query.

• You may place your left 4-finger to authenticate and login into the registration client.