Last updated
Was this helpful?
Last updated
Was this helpful?
The BioSDK diagram illustrates how MOSIP integrates biometric devices for registration and authentication. It shows the flow of biometric data from capture devices through the Secure Biometric Interface (SBI) to the BioSDK, which performs quality checks, deduplication, and operator authentication.
For registration, signed biometrics are sent to the MOSIP backend, where the BioSDK ensures data quality, ABIS handles deduplication, and ID Auth manages 1:1 matching. During authentication, encrypted biometrics are verified via the authentication app. Device management, including registration, deregistration, and key rotation, is handled by the Device Management Server.
Registration Client.
Backend quality check.
Biometric authentication during onboarding (internal auth).
ID Authentications.
BioSDK service: TBD.
The library is used by the to perform 1:N match, segmentation, extraction, etc. For more information on integration with Registration Client, refer to the .
A simulation of this library is available as . The same is installed in the .
For 1:1 match and quality check of biometrics at the MOSIP backend, the BioSDK must be running as a service that can be accessed by and . The service exposes REST APIs specified .
A has been provided. The mock service loads internally on the startup and exposes the endpoints to perform 1:N match, segmentation, and extraction as per .
The service may be packaged as a docker running inside the or running separately on a server. The scalability of this service must be taken care of depending on the load on the system, i.e., the rate of enrolment and ID authentication.
BioSDK library:
BioSDK server request/response may be tested using the .
The following properties in needs to be updated to integrate the BioSDK library and service with MOSIP.
