Skip to content

TASK: Add one-time TOTP provisioning response for MFA enrollment #265

Closed
digital-bank-java/mfa-service
#21

Description

@ramioooz

Type: Task
Parent: STORY: Require MFA for high-value internal, domestic, and international transfers (#56)
Epic: Step-Up Authorization
Sprint: Sprint 4 - Secure Customer Access and Step-Up Authorization
Service: mfa-service
Priority: P0

Outcome

Make authenticated MFA enrollment usable by an approved authenticator while preserving secret confidentiality.

Scope

  • Return a one-time provisioning representation from enrollment creation so a client can configure TOTP.
  • Never provide a read or recovery endpoint for the raw secret.
  • Never log or persist the secret in application responses beyond the creation response; keep encrypted-at-rest persistence unchanged.
  • Document the response handling and SIT acceptance workflow without committing credentials or OTP values.

Definition of Done

  • Enrollment creation returns the provisioning data exactly once to the authenticated owner.
  • Existing enrollment and challenge response contracts remain compatible except for additive creation fields.
  • Focused verification proves provisioning data is present at creation, absent from subsequent lifecycle responses, and does not expose secret material in logs or error responses.
  • The transfer-bound MFA acceptance can activate an enrollment, verify a challenge, publish assurance, and resume the transfer saga in local SIT.

This task is required to complete Sprint 4 #56 and #208. AWS/UAT/PROD deployment remains deferred.

Activity

  1. ramioooz commented on Sep 10, 2026

    @ramioooz
    MemberAuthor

    Implementation is ready in mfa-service PR #21: digital-bank-java/mfa-service#21

    The approved one-time TOTP provisioning URI is returned only on enrollment creation with no-store/no-cache headers. Later lifecycle responses omit it, and application string representations redact it. No secret or URI value is included in this tracking comment.

    Verification: ./mvnw verify passed with 46 unit tests and 20 integration tests.

  2. self-assigned this
    on Sep 10, 2026
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

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions