[MS-1127] Multi-Factor ID: architecture groundwork#1358
Merged
alexandr-simprints merged 9 commits intoSep 18, 2025
Merged
Conversation
|
luhmirin-s
approved these changes
Sep 18, 2025
5 tasks
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
Notable changes
This PR only contains the necessary groundwork to support the MF-ID in the Enrolment and Identification workflows. Considering the size of the feature, we would like to limit the scope to make PRs easier to review. What has been added/changed:
1. external-credential moduleAdding new
:feature:external-credentialmodule that will contain everything related to the user-facing part of the MF-ID2. Navigation3. Controller fragment + child fragments4. MF-ID Step added5. Orchestrator UpdatesenrolmentSubjectId: Stringfield is added. When building steps during Enrolment, the MF-ID step requires to know whatsubjectIdto use if user links the credential. Previously, thesubjectIdwas generated inSubjectFactory::buildSubjectFromCaptureResultscalled fromCreateEnrolResponseUseCase:val subjectId = UUID.randomUUID().toString()Now, the same assignment is done in advance to allow passing it to the MF-ID step instead of dynamically updating the MF-ID step in Orcherstrator
Testing guidance
MF-IDin project configurationScanner Selectionscreen is displayed after the biometric capture stepAdditional work checklist