MOSIP-35150: Enhancement - Updating Biometric flow to enable auto reject in case of single duplicate record

[Ivanmeneges]

Purpose:

To enhance the biometric update process by ensuring that only valid updates are accepted. The system should verify the UINs during the bio dedupe stage and reject packets with mismatched UINs, with the ability to configure the auto-reject feature as needed.

Basic Flow:

1. During the update flow, a biometric match is found at the bio dedupe stage.

2. If exactly one match is found:

• Retrieve the RID/AID of the matched record.

• Identify the mapped UIN associated with this record.

• Compare the retrieved UIN with the UIN specified in the incoming packet.

1. If the UINs match, proceed with the update process.

2. If the UINs differ, auto-reject the packet.

3. The auto-reject process should be configurable

Acceptance Criteria:

1. When a single biometric match is found and associated UIN does not match with incoming packets, auto reject the packet.

2. The auto-reject feature must be configurable, allowing administrators to enable or disable automatic rejection based on UIN mismatches.

3. If more than one match is found in the bio de dupe stage, the packet should be directed to the manual adjudication stage as per camel route workflow.

Scenarios:

|### Scenarios|### System Behaviour|
|No match of RID/AID found in bio dedupe|allowing to update|
|One match of RID/AID found at bio dedupe stage. UIN of the duplicate match is same as the update packet UIN|Biometric details should be updated|
|One match of RID/AID found at bio dedupe, but UIN of the duplicate match is different from update packet UIN|Biometric details should not be updated and packet to be auto rejected|
|More than one match of RID/AID found at bio dedupe stage, all UIN of duplicate matches are same as update packet UIN|Biometric details should be updated|
|More than one match of RID/AID found at bio dedupe stage, all duplicate matches have the same UIN but, they does not matches with update packet UIN|Biometric details should not be updated and packet to be auto rejected|
|More than one match of RID/AID found at bio dedupe stage, all duplicate matches possess different UINs. Among that one UIN matches with update packet UIN|Redirect to Manual Adjudication|
|More than one match of RID/AID found at bio dedupe stage, all duplicate matches possess different UINs. Among that no UIN matches with update packet UIN|Redirect to Manual Adjudication|
|One match of RID/AID found at bio dedupe stage, found AID/RID is in progress status and RID & UIN mapping is not done|Redirect to Manual Adjudication|
|More than one match of RID/AID found at bio dedupe stage, Among them one of the RID is in progress state & mapping is not done in repo|Redirect to Manual Adjudication|
|More than one match of RID/AID found at bio dedupe stage, All RID is in progress state & mapping is not done in repo|Redirect to Manual Adjudication|

Unit test cases needed to be created for the above-mentioned scenarios as well

Note:

New property to be added in Bio-dedupe stage which can configured in the registration-processor-default.properties

This property auto rejects the update packet if above property value is true in below case:

• Matched RIDs are associated with single UIN which is not equal to update packet UIN.

By default this property value is false. Post changing this property, we need to restart the stage-3 service to reflect the changed value.

🔗 Linked Issues

ISSUE

• MOSIP-34112
  Status: Closed
• MOSIP-35175
  Status: New Dev
• MOSIP-35207
  Status: Assigned

[Ivanmeneges]

Hemant C Vadher commented: [~accountid:712020:a354eedc-e17e-400c-b961-a8a3f716ad4f] for your prioritisation.

[Ivanmeneges]

Nidhi Kumari commented: Assigning to QA as part of Biometric Update Bug fix to verify

[Ivanmeneges]

varaniya commented: As discussed, the property “{{registration.processor.biometrics-update.single-match.auto-reject.enabled}}" is not implemented as part of this story and take up as additional enhancement.

cc: [~accountid:5f3ce670333edb0043b2b9e5] [~accountid:61482f457a3c8800672137a3]