[MS-1271] Identification results now always return the MF-ID credential matches first, ignoring the confidence threshold#1496
Merged
Conversation
…al matches first, ignoring the confidence threshold. This way the callout app ˆcan display the credential holder GUIDs alongside their match score
BurningAXE
reviewed
Dec 8, 2025
BurningAXE
approved these changes
Dec 8, 2025
There was a problem hiding this comment.
Pull request overview
This PR fixes a bug (MS-1271) where credential matches (e.g., NHIS/MF-ID matches) were incorrectly filtered out by the confidence threshold during 1:N identification. The fix ensures that credential-linked GUIDs are always returned at the top of the identification results list, regardless of their matching score.
Key Changes
- Credential matches now bypass confidence threshold filtering and are always included in results
- Credential results are returned before biometric (1:N) match results
- Removed unused
projectConfigurationparameter frommapToMatchResultsfunction
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
feature/orchestrator/src/main/java/com/simprints/feature/orchestrator/usecases/response/CreateIdentifyResponseUseCase.kt |
Modified identification response logic to always return credential matches regardless of confidence score, and restructured to place credential results before biometric matches |
feature/orchestrator/src/test/java/com/simprints/feature/orchestrator/usecases/response/CreateIdentifyResponseUseCaseTest.kt |
Consolidated and updated tests for credential matching behavior, including testing combined face and fingerprint credential results |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
luhmirin-s
approved these changes
Dec 9, 2025
…matches and 1:N matches are returned in the identification response. All credentials are also now properly sorted by confidence score DESC
|
luhmirin-s
pushed a commit
that referenced
this pull request
Jan 19, 2026
…al matches first, ignoring the confidence threshold (#1496) * [MS-1271] Identification results now always return the MF-ID credential matches first, ignoring the confidence threshold. This way the callout app ˆcan display the credential holder GUIDs alongside their match score * [MS-1271] Adding a test case covering scenario where both credential matches and 1:N matches are returned in the identification response. All credentials are also now properly sorted by confidence score DESC * [MS-1271] Fixing tests # Conflicts: # feature/orchestrator/src/main/java/com/simprints/feature/orchestrator/usecases/response/CreateIdentifyResponseUseCase.kt # feature/orchestrator/src/test/java/com/simprints/feature/orchestrator/usecases/response/CreateIdentifyResponseUseCaseTest.kt
luhmirin-s
pushed a commit
that referenced
this pull request
Jan 20, 2026
…al matches first, ignoring the confidence threshold (#1496) * [MS-1271] Identification results now always return the MF-ID credential matches first, ignoring the confidence threshold. This way the callout app ˆcan display the credential holder GUIDs alongside their match score * [MS-1271] Adding a test case covering scenario where both credential matches and 1:N matches are returned in the identification response. All credentials are also now properly sorted by confidence score DESC * [MS-1271] Fixing tests # Conflicts: # feature/orchestrator/src/main/java/com/simprints/feature/orchestrator/usecases/response/CreateIdentifyResponseUseCase.kt # feature/orchestrator/src/test/java/com/simprints/feature/orchestrator/usecases/response/CreateIdentifyResponseUseCaseTest.kt
luhmirin-s
pushed a commit
that referenced
this pull request
Jan 20, 2026
…al matches first, ignoring the confidence threshold (#1496) * [MS-1271] Identification results now always return the MF-ID credential matches first, ignoring the confidence threshold. This way the callout app ˆcan display the credential holder GUIDs alongside their match score * [MS-1271] Adding a test case covering scenario where both credential matches and 1:N matches are returned in the identification response. All credentials are also now properly sorted by confidence score DESC * [MS-1271] Fixing tests # Conflicts: # feature/orchestrator/src/main/java/com/simprints/feature/orchestrator/usecases/response/CreateIdentifyResponseUseCase.kt # feature/orchestrator/src/test/java/com/simprints/feature/orchestrator/usecases/response/CreateIdentifyResponseUseCaseTest.kt
luhmirin-s
pushed a commit
that referenced
this pull request
Jan 20, 2026
…al matches first, ignoring the confidence threshold (#1496) * [MS-1271] Identification results now always return the MF-ID credential matches first, ignoring the confidence threshold. This way the callout app ˆcan display the credential holder GUIDs alongside their match score * [MS-1271] Adding a test case covering scenario where both credential matches and 1:N matches are returned in the identification response. All credentials are also now properly sorted by confidence score DESC * [MS-1271] Fixing tests # Conflicts: # feature/orchestrator/src/main/java/com/simprints/feature/orchestrator/usecases/response/CreateIdentifyResponseUseCase.kt # feature/orchestrator/src/test/java/com/simprints/feature/orchestrator/usecases/response/CreateIdentifyResponseUseCaseTest.kt
luhmirin-s
pushed a commit
that referenced
this pull request
Jan 21, 2026
…al matches first, ignoring the confidence threshold (#1496) * [MS-1271] Identification results now always return the MF-ID credential matches first, ignoring the confidence threshold. This way the callout app ˆcan display the credential holder GUIDs alongside their match score * [MS-1271] Adding a test case covering scenario where both credential matches and 1:N matches are returned in the identification response. All credentials are also now properly sorted by confidence score DESC * [MS-1271] Fixing tests # Conflicts: # feature/orchestrator/src/main/java/com/simprints/feature/orchestrator/usecases/response/CreateIdentifyResponseUseCase.kt # feature/orchestrator/src/test/java/com/simprints/feature/orchestrator/usecases/response/CreateIdentifyResponseUseCaseTest.kt
luhmirin-s
pushed a commit
that referenced
this pull request
Jan 21, 2026
…al matches first, ignoring the confidence threshold (#1496) * [MS-1271] Identification results now always return the MF-ID credential matches first, ignoring the confidence threshold. This way the callout app ˆcan display the credential holder GUIDs alongside their match score * [MS-1271] Adding a test case covering scenario where both credential matches and 1:N matches are returned in the identification response. All credentials are also now properly sorted by confidence score DESC * [MS-1271] Fixing tests # Conflicts: # feature/orchestrator/src/main/java/com/simprints/feature/orchestrator/usecases/response/CreateIdentifyResponseUseCase.kt # feature/orchestrator/src/test/java/com/simprints/feature/orchestrator/usecases/response/CreateIdentifyResponseUseCaseTest.kt
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



JIRA ticket
Will be released in: 2025.4.0
Root cause analysis (for bugfixes only)
First known affected version: 2025.4.0
When running a 1:N identification in the scenario where:
SID fails to return the NHIS-linked GUID. Instead, the result set is empty. This is because the credential results were filtered out by the threshold. We need to always include the GUIDs linked to credential regardless of the matching score.
Notable changes
Identificationlist, regardless of their matching scoreTesting guidance
AandBwith different biometrics, and different credentials.A, and credentials of the subjectBAdditional work checklist