Biometric SDK
Biometric SDK
Overview
<<<<<<< HEAD
Usage of Biometric SDK in Registration Client
Local dedupe check between operators and operator-resident biometrics.
Local operator biometric authentications.
Extraction of biometric template from operator's raw biometrics to store in local derby DB.
To get quality score for the SBI captured biometrics.
For more information on intergation with Registration Client, refer Registration Client Biometric SDK Integration Guide.
Applications
Registration Client.
Backend quality check.
Biometric authentication during onboarding (internal auth).
ID Authentications.
Biometric SDK library
The library is used by Registration Client to perform 1:N match, segmentation, extraction etc. For more information on intergation with Registration Client, refer Registration Client Biometric SDK Integration Guide.
A simulation of this library is available as Mock BioSDK. The same is installed in MOSIP sandbox.
Biometric SDK service
For 1:1 match and quality check of biometrics at MOSIP backend, the BioSDK must be running as a service that can be accessed by Registration Processor and IDA Internal Services. The service exposes REST APIs specified here.
A simulation (mock) service has been provided. The mock service loads mock BioSDK internally on the startup and exposes the endpoints to perform 1:N match, segmentation, extraction as per IBioAPI.
The service may be packaged as a docker running inside MOSIP Kubernetes cluster or running separately on a server. It is important that the scalability of this service is taken care depending on the load on the system, i.e., the rate of enrolment and ID authentication.
API
BioSDK library: IBioAPI.
BioSDK service: TBD.
Testing kit
BioSDK server request/response may be tested using BioSDK testing kit.
Configuration
The following properties in application-default.properties
needs to be updated to integrate BioSDK library and service with MOSIP.
1.2.0
Last updated