MS-1228 Enrolment Record update event fix

[luhmirin-s]

JIRA ticket
Will be released in: version

Notable changes

• Ensuring that there is exactly one EnrolmentUpdateEvent per session for the last received subject ID confirmation. If the confirmation was for "None", all of the update events are removed from the session.
• Removing all EnrolmentUpdateEvent and reverting credential links on the last biometric enrolment.
• Added a method to delete events in the current session.
• Added a method to remove credentials from the record by the IDs saved in EnrolmentUpdateEvent (explicitly not by value to avoid accidentally removing values from different sessions).

Testing guidance

• Set the device to offline mode to prevent upsync during the test
• Do an identification flow with an external credential scan in such a way that there are several subject IDs returned (save several of the IDs).
• Send confirmation intent with one of the IDs, confirm addition of the external credential. In the troubleshooting screen, check the events in the last intent - it should contain EnrolmentUpdateEvent for the last confirmation.
• Send confirmation with another subject ID, confirm the addition of the credentials again. In the troubleshooting screen, check the events in the last intent - it should still contain a single EnrolmentUpdateEvent for the last confirmation.
• Repeat as many times as you want - there should always be a single EnrolmentUpdateEvent for the last confirmation.
• Send confirmation with "none_selected" instead of UUID. There should be no credential attachment dialog and no EnrolmentUpdateEvent for the last confirmation events.

Additional work checklist

• Effect on other features and security has been considered
• Design document marked as "In development" (if applicable)
• External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
• Test cases in Testiny are up to date (or ticket created)
• Other teams notified about the changes (if applicable)

[ybourgery]

I think you are missing the use-case where we are doing a (or several) confirmation followed by an enrolment last biometrics, in this case it should also remove the existing EnrolmentUpdate events

[luhmirin-s]

@ybourgery added the same session cleanup to enrol last as well.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

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

See analysis details on SonarQube Cloud

[alexandr-simprints]

Great job, thanks for addressing this issue!