[MS-1290] Each credential match now produces a OneToOne event

[alexandr-simprints]

JIRA ticket
Will be released in: 2025.4.0

Root cause analysis (for bugfixes only)

First known affected version: 2025.4.0
There were no OneToOneEvent instances for credential matches.

Notable changes

Now, when a biometric probe that, linked to the credential, is being matched against a biometric probe taken during the workflow, a OneToOne match event is saved.

Testing guidance

• Enrol a subject A with a credential C
• Identify biometrics of subject B, and use the same credential C
• Make sure OneToOne event is created with low confidence score

Additional work checklist

• Effect on other features and security has been considered
• Other teams notified about the changes (if applicable)

[ybourgery]

I think the timestamp are not the most accurate to represent what is actually happening

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

[Copilot]

Using orEmpty() on probeReferenceId silently converts null to an empty string. Consider whether an empty string is semantically correct for this field, or if null should be preserved or handled differently. If an empty string is intentional when the value is absent, this is acceptable.

Suggested change

	probeBiometricReferenceId = match.probeReferenceId.orEmpty(),
	probeBiometricReferenceId = match.probeReferenceId,

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
87.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud