Tech5 Windows SDK helps to check the quality of biometrics, 1:1 verify and 1:N search capabilities for the enrollment client. Quality check is used to access quality of the capture to ensure only good quality of biometrics to be enrolled. 1:N is used for operator search to ensure operator biometrics are not sent as subjects data.1:1 is used for operator authentication.

This is a step-by-step guide on how to configure the tech5 Windows Biosdk with the registration client.
Tech5 Windows Client OmniMatch BioSDK(v5.0.0):

(blue star) Instructions

  1. Compress the tech5 jars into a single zip file and name it sdkDependecy.zip.

  2. Go to the Mosip artifactory project, navigate to the directory “artifactory-ref-impl/artifacts/src/sdk/” and create a new folder named tech5. Under this folder add the zip file created in Step #1.

  3. Modify the artifactory project’s docker file to include the path of the sdkDependecy zipped folder. I.e add the following code to the docker file.

    # environment variable for tech5 jar path
    ENV tech5_zip_path=${base_path}/libs-release-local/sdk/tech5
    
    COPY /src/sdk/tech5/* ${tech5_zip_path}/
  4. Build and deploy the artifactory project and Restart the artifactory server in Rancher.

  5. Next in the registration client deployment .yml file, add the name and URL of the tech5 SDK to the environment list.

  6. Build and deploy the registration client and Restart the registration-service in Rancher.

  7. Obtain the native tech5 folder and extract it.

  8. Copy the folder path of the extracted folder in Step #7 and add it to your windows system environment variables inside the path as shown in the image

Example:
D:\MOSIP\Mosip Environment\WuriGuinea\Tech5 Windows SDK\Tech5\T5OmniMatchBioSDK

D:\MOSIP\Mosip Environment\WuriGuinea\Tech5 Windows SDK\Tech5\T5OmniMatchBioSDK\bin

D:\MOSIP\Mosip Environment\WuriGuinea\Tech5 Windows SDK\Tech5\T5OmniMatchBioSDK\lib

  1. To use the T5-BioSDK, system must have valid license. Follow below steps to create license requests.

Request files will be generated in the location where you open the command prompt

In the latest version of tech5 BioSDK there is only one license file for all the modalities.

  1. Place the  config.properties (Take the config properties from tech5 native folder) and license file to the root folder of the registration client.

  2. Inside the config.properties change the folder path and licence file path and save.

  3. Modify the Registration client run.bat file with tech5 biosdk path in application start command file will look like as shown below.

    @echo off
    if exist .UNKNOWN_JARS (
    FOR /F "tokens=* delims=" %%x in (.UNKNOWN_JARS) DO DEL /Q lib\%%x
    )
    if exist .TEMP (
    echo Starting Registration Client after Upgrade
    xcopy /f/k/y/v/q .TEMP lib && rmdir /s /q .TEMP && start jre\bin\javaw -Xmx2048m -Xms2048m -Dai.tech5.biosdk.provider.config=./config.properties -DuseMosipLogger=true -Dfile.encoding=UTF-8 -cp lib/*;/* io.mosip.registration.controller.Initialization > startup.log 2>&1
    ) else (
    echo Starting Registration Client
    start jre\bin\javaw -Xmx2048m -Xms2048m -Dfile.encoding=UTF-8 -Dai.tech5.biosdk.provider.config=./config.properties -DuseMosipLogger=true -cp lib/*;/* io.mosip.registration.controller.Initialization > startup.log 2>&1
    )
    
  4. Modify the properties in the mosip-config repository, registration-default.properties to enable local deduplication and then restart the config server in the rancher.

    mosip.biometric.sdk.providers.finger.tech5.classname=ai.tech5.mosip.biosdk.provider.OmniMatchBioSDKProvider
    mosip.biometric.sdk.providers.finger.tech5.version=0.9
    mosip.biometric.sdk.providers.finger.tech5.args=
    mosip.biometric.sdk.providers.finger.tech5.threshold=60
    mosip.biometric.sdk.providers.iris.tech5.classname=ai.tech5.mosip.biosdk.provider.OmniMatchBioSDKProvider
    mosip.biometric.sdk.providers.iris.tech5.version=0.9
    mosip.biometric.sdk.providers.iris.tech5.args=
    mosip.biometric.sdk.providers.iris.tech5.threshold=60
    mosip.biometric.sdk.providers.face.tech5.classname=ai.tech5.mosip.biosdk.provider.OmniMatchBioSDKProvider
    mosip.biometric.sdk.providers.face.tech5.version=0.9
    mosip.biometric.sdk.providers.face.tech5.args=
    mosip.biometric.sdk.providers.face.tech5.threshold=60
    
    mosip.biometric.sdk.provider.finger.classname=ai.tech5.mosip.biosdk.provider.OmniMatchBioSDKProvider
    mosip.biometric.sdk.provider.iris.classname=ai.tech5.mosip.biosdk.provider.OmniMatchBioSDKProvider
    mosip.biometric.sdk.provider.face.classname=ai.tech5.mosip.biosdk.provider.OmniMatchBioSDKProvider
    
    mosip.registration.mds.deduplication.enable.flag=Y
    

Tech5 Windows Client BioSDK(v4.3.0):

(blue star) Instructions

  1. Compress the tech5 jars into a single zip file and name it sdkDependecy.zip.

  2. Go to the Mosip artifactory project, navigate to the directory “artifactory-ref-impl/artifacts/src/sdk/” and create a new folder named tech5. Under this folder add the zip file created in Step #1.

  3. Modify the artifactory project’s docker file to include the path of the sdkDependecy zipped folder. I.e add the following code to the docker file.

    # environment variable for tech5 jar path
    ENV tech5_zip_path=${base_path}/libs-release-local/sdk/tech5
    
    COPY /src/sdk/tech5/* ${tech5_zip_path}/
  4. Build and deploy the artifactory project.

  5. Next in the registration client deployment .yml file, add the name and URL of the tech5 SDK to the environment list.

  6. Build and deploy the registration client.

  7. Obtain the native tech5 folder and extract it.

  8. Copy the folder path of the extracted folder in Step #7 and add it to your windows system environment variables list with under a new variable named FACE_SDK_BIN_ROOT.

  9. To use the T5-BioSDK, system must have valid license. Follow below steps to create license requests.

    Open the command prompt and run the below command to generate the face & finger license request files

    face_sdk_utils --request --out TPM_new_face_sdk.req
    fingersdk_utils --request --output TPM_new_finger_sdk.req

Request files will be generated in the location where you open the command prompt

Send these request files to TECH5 team to get the licenses

  1. Copy the files config.properties, finger_sdk.lic, face_sdk.lic and iris_sdk.lic files from the native folder to the root folder of the registration client.

    config.properties file :

    # General Provider Configuration
    ai.tech5.biosdk.provider.general.debug.outputToFile= false
    ai.tech5.biosdk.provider.general.load.faceSdk= false
    ai.tech5.biosdk.provider.general.load.fingerSdk= true
    ai.tech5.biosdk.provider.general.load.irisSdk= true
    
    # Face SDK Configuration
    # 0-20 range
    ai.tech5.biosdk.provider.face.tc.threshold= 6.0
    ai.tech5.biosdk.provider.face.tc.detectorConfidence= 0.9f
    ai.tech5.biosdk.provider.face.tc.batchSize= 1
    ai.tech5.biosdk.provider.face.tc.computeDevice= -1
    ai.tech5.biosdk.provider.face.tc.faceSelectorAlg= 2
    
    ai.tech5.biosdk.provider.face.matcher.mMatcher.firListHint= 100000
    ai.tech5.biosdk.provider.face.matcher.mMatcher.tableCode= gn
    ai.tech5.biosdk.provider.face.matcher.mBuilder.version= 105
    
    ai.tech5.biosdk.provider.face.tc.version.quality= 100
    ai.tech5.biosdk.provider.face.tc.version.faceDetector= 200
    ai.tech5.biosdk.provider.face.tc.version.alignment= 103
    ai.tech5.biosdk.provider.face.tc.version.builder= 105
    ai.tech5.biosdk.provider.face.tc.version.ageGender= 100
    
    ai.tech5.biosdk.provider.face.tc.remoteLicensingCachePath= "face_sdk.lic"
    ai.tech5.biosdk.provider.face.tc.remoteLicensingToken= "4293EDB66AE2C"
    ai.tech5.biosdk.provider.face.tc.useRemoteLicensing= false
    
    ai.tech5.biosdk.provider.face.tc.checker.useBackgroundChecker= true
    ai.tech5.biosdk.provider.face.tc.checker.useBlurChecker= true
    ai.tech5.biosdk.provider.face.tc.checker.useFaceColorChecker= true
    ai.tech5.biosdk.provider.face.tc.checker.useGlassesSmileOcclusionChecker= true
    ai.tech5.biosdk.provider.face.tc.checker.useHotSpotsChecker= true
    ai.tech5.biosdk.provider.face.tc.checker.useMaskChecker= true
    ai.tech5.biosdk.provider.face.tc.checker.useOverexposureChecker= true
    ai.tech5.biosdk.provider.face.tc.checker.useRedEyesChecker= true
    ai.tech5.biosdk.provider.face.tc.checker.useRotationChecker= true
    
    
    # Finger SDK Configuration
    #0-20 range
    ai.tech5.biosdk.provider.finger.threshold= 6.0
    ai.tech5.biosdk.provider.finger.search.searchSpeed = 3
    ai.tech5.biosdk.provider.finger.search.maxAngle= 50
    ai.tech5.biosdk.provider.finger.search.maxDisp = 50
    ai.tech5.biosdk.provider.finger.fingerToken= "finger_sdk.lic"
    
    
    # Iris SDK Configuration
    #0-20 range
    ai.tech5.biosdk.provider.iris.threshold= 0.2
    ai.tech5.biosdk.provider.iris.handlerThreadCount= 6
    
    

  1. Modify the properties in the mosip-config repository, registration-default.properties to enable local deduplication.

    #Admin Setting to turn local deduplication check On or Off. If y, dedupe check is turned on. If n, dedupe check is truned off.
    mosip.registration.mds.deduplication.enable.flag=Y
    
    ## SDK configurations
    #SDK implementation class for modality
    mosip.biometric.sdk.provider.finger.classname=ai.tech5.mosip.biosdk.provider.T5BioSDKProvider
    mosip.biometric.sdk.provider.iris.classname=ai.tech5.mosip.biosdk.provider.T5BioSDKProvider
    mosip.biometric.sdk.provider.face.classname=ai.tech5.mosip.biosdk.provider.T5BioSDKProvider
  2. Finally, add the following properties, also in registration-default.properties, and restart the mosip-config server.

    mosip.biometric.sdk.providers.finger.tech5.classname=ai.tech5.mosip.biosdk.provider.T5BioSDKProvider
    mosip.biometric.sdk.providers.iris.tech5.classname=ai.tech5.mosip.biosdk.provider.T5BioSDKProvider
    mosip.biometric.sdk.providers.face.tech5.classname=ai.tech5.mosip.biosdk.provider.T5BioSDKProvider

Please download the latest Tech5 SDK to enable this feature.

(blue star) Related articles

The content by label feature automatically displays related articles based on labels you choose. To edit options for this feature, select the placeholder and tap the pencil icon.