Skip to content

TASK: Implement transfer-bound MFA challenge lifecycle #206

Closed

Description

@ramioooz

Objective

Bind MFA step-up challenges to one transfer risk decision and immutable transfer intent.

Scope

  • Add internal transfer-bound challenge creation and verification endpoints.
  • Bind transfer ID, decision ID, authenticated subject, account references, normalized amount/currency, policy version, and correlation ID.
  • Persist the binding and enforce mismatch rejection and single-use verification.
  • Keep Transaction Service responsible for transfer workflow continuation; MFA returns assurance evidence only.
  • Keep API Gateway routing and Auth Service session orchestration as follow-up integration work.

Verification

  • Focused controller coverage for creation, successful verification, and binding mismatch.
  • Persistence coverage for database rehydration of the binding.
  • Full Maven verify and Helm lint/render.

Dependencies

This task is intentionally implemented as a dependent pull request. Merge the durable persistence PR first; no delay is required before merging this PR.

Activity

  1. self-assigned this
    on Sep 4, 2026
  2. added theissue type on Sep 4, 2026
  3. ramioooz commented on Sep 4, 2026

    @ramioooz
    MemberAuthor

    Important merge-target correction: the original MFA implementation PR digital-bank-java/mfa-service#10 was merged into feature/mfa-postgres-persistence, not main. Corrective mainline PR is now open: digital-bank-java/mfa-service#13.

    Verification passed on the promoted change: 42 unit-phase tests, 19 integration tests, Helm lint/render, and git diff --check. Merge #13 before the final MFA SIT image rollout; no fixed delay is required after merge.

  4. ramioooz commented on Sep 4, 2026

    @ramioooz
    MemberAuthor

    Completed by merged mfa-service#9 and mfa-service#10. The durable persistence and transfer-bound challenge lifecycle are implemented and verified by the merged PR checks. API Gateway routing, Transaction continuation, and full SIT event rollout remain separate integration work under the parent stories and rollout tasks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions