Quality SDK: Support for 3rd party SDK to measure quality of biometrics captured

[Pragya279]

User Story: Support for Third-Party SDKs to Measure Biometric Capture Quality

As a Registration Operator
I want the Registration Client to seamlessly integrate with third-party biometric quality assessment SDKs
So that the system can automatically evaluate the quality of captured biometrics (fingerprints, iris, face) and ensure they meet the required thresholds before submission.

Problem / Need

Biometric capture quality is critical for accurate deduplication and reliable identity creation. However, the existing workflow relies on device-specific quality checks or operator judgement, which may be inconsistent or insufficient.
To ensure high-quality, standards-compliant biometrics across all deployments, the Registration Client must support plug-and-play integration of industry-approved third-party quality assessment SDKs.

Feature Description

This feature introduces the ability for MOSIP Registration Client to:

Integrate with External Quality SDKs

Provide an extensible interface (adapter) that allows any compliant third-party biometric quality SDK (e.g., NFIQ/NFIQ2 for fingerprints, ISO/IEC quality algorithms) to be plugged in.

Ensure no tight coupling with any vendor implementation.

Trigger Quality Checks During Capture

After biometrics are captured (fingerprint slap, iris pair, or face image), the client automatically invokes the integrated SDK for quality scoring.

SDK returns a score and/or pass–fail results.

Display Quality Feedback to Operators

Operators see clear indicators (score, color coding, "Pass"/"Fail") immediately after capture.

If quality is below threshold, the operator is prompted to recapture.

Apply Configurable Thresholds

Administrators can define the minimum acceptable quality scores in configuration files or server-managed policies.

Thresholds may differ by biometric modality.

Record Quality Metadata

The quality score and related metrics from the SDK are stored as part of the biometric packet.

Supports auditing and future reference.

Fallback & Error Handling

If the SDK fails or is unavailable, the system falls back to default device quality checks (if enabled).

Appropriate warnings are shown to the operator.

Acceptance Criteria

AC1: The Registration Client can integrate with at least one external biometric quality SDK via a standardized interface.

AC2: Upon biometric capture, the SDK is automatically invoked, and the quality score is returned.

AC3: Operators see quality results in real-time with clear visual feedback.

AC4: The system blocks submission if the biometric quality is below the configured threshold (configurable behaviour).

AC5: Quality metadata is stored in the captured packet.

AC6: System handles SDK errors gracefully and provides fallback behaviour.

Examples of User Flow

Operator captures applicant’s fingerprints.

Registration Client sends the fingerprint data to the integrated SDK.

SDK returns: score=78, status="PASS" against threshold 70.

UI shows a green indicator → Operator proceeds.

For iris capture, SDK returns score=22, status="FAIL" against threshold 40.

UI prompts: “Low iris quality detected. Please recapture.”