Skip to content

[MS-1127] Multi-Factor ID: architecture groundwork#1358

Merged
alexandr-simprints merged 9 commits into
CORE-3404-search-verifyfrom
MS-1127-mf-id-implementation-architecture-groundwork
Sep 18, 2025
Merged

[MS-1127] Multi-Factor ID: architecture groundwork#1358
alexandr-simprints merged 9 commits into
CORE-3404-search-verifyfrom
MS-1127-mf-id-implementation-architecture-groundwork

Conversation

@alexandr-simprints
Copy link
Copy Markdown
Contributor

@alexandr-simprints alexandr-simprints commented Sep 10, 2025

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 module

Adding new :feature:external-credential module that will contain everything related to the user-facing part of the MF-ID

2. Navigation

  • Two navigation graphs were added: external (to enter the step) and internal (for sub-steps, the same way it is done with face).

3. Controller fragment + child fragments

  • Controller fragment is in charge of the entire MF-ID 'step', and hosts the child fragments
  • Child fragments are not yet implemented. Each fragment will get its own PR.

4. MF-ID Step added

  • MF-ID step is added to the list of steps if enabled in the project configuration
  • Only Enrolment and Identification flows may have the MF-ID step

5. Orchestrator Updates

  • enrolmentSubjectId: String field is added. When building steps during Enrolment, the MF-ID step requires to know what subjectId to use if user links the credential. Previously, the subjectId was generated in SubjectFactory::buildSubjectFromCaptureResults called from CreateEnrolResponseUseCase:
    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

  • Enable MF-ID in project configuration
  • Start enrolment
  • Verify that Scanner Selection screen is displayed after the biometric capture step

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)

@sonarqubecloud
Copy link
Copy Markdown

@alexandr-simprints alexandr-simprints merged commit 4320188 into CORE-3404-search-verify Sep 18, 2025
13 checks passed
@alexandr-simprints alexandr-simprints deleted the MS-1127-mf-id-implementation-architecture-groundwork branch September 18, 2025 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants