Skip to content

TASK: Provision SIT MFA persistence prerequisites #204

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

Description

@ramioooz

Objective

Provision the non-secret SIT prerequisites required by the durable MFA persistence implementation.

Scope

  • Create the mfa_service logical database in the shared SIT PostgreSQL instance.
  • Create the mfa-service-secrets Kubernetes Secret in digital-bank-sit with the externally generated MFA_TOTP_ENCRYPTION_KEY value.
  • Do not commit, export, or place the encryption key in Git history, Helm values, Config Server, logs, or issue comments.
  • Document the key generation, injection, rotation, and removal procedure in the local SIT runbook.
  • Roll out MFA Service after mfa-service#9 and verify startup, Flyway migration, and health.

Acceptance Criteria

  • The database exists and is owned by the configured MFA database user.
  • The Secret exists with key MFA_TOTP_ENCRYPTION_KEY and is readable only by the intended SIT workload.
  • MFA Service starts successfully with PostgreSQL persistence and does not log the key.
  • The secret value is supplied out-of-band and is never stored in a tracked file.
  • Rollback/removal instructions are documented.

Dependencies

This is an SIT operational prerequisite. UAT/PROD secret delivery remains deferred to the AWS readiness sprint.

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

    Implementation PR is open:\n- SIT PostgreSQL logical database and external MFA Secret runbook: https://github.com/digital-bank-java/infra-sit/pull/30\n- Related MFA producer: https://github.com/digital-bank-java/mfa-service/pull/11\n- Related SIT config: https://github.com/digital-bank-java/config-repo/pull/40\n\nMerge #30 before rolling out MFA Service in SIT. Create the Secret out-of-band after merge; no secret value is stored in Git.

  4. ramioooz commented on Sep 4, 2026

    @ramioooz
    MemberAuthor

    Verification update (2026-09-04):

    • infra-sit#30 is merged.
    • PostgreSQL and Auth Secrets are present in digital-bank-sit.
    • mfa-service-secrets is not yet present in digital-bank-sit.
    • The MFA logical database creation is delivered by the merged infrastructure change.

    Task remains In progress. Before rolling out MFA Service, create the external mfa-service-secrets Secret using the reviewed runbook; do not record or print its value. Then deploy MFA Service and verify startup.

  5. ramioooz commented on Sep 4, 2026

    @ramioooz
    MemberAuthor

    Verification update (2026-09-04):

    • infra-sit#30 is merged.
    • The documented throwaway mfa-service-secrets Secret was created in digital-bank-sit using the MFA_TOTP_ENCRYPTION_KEY key. Its value was not printed, recorded, or committed.
    • The mfa_service logical PostgreSQL database was created in the existing SIT Postgres instance because the persistent volume predates the merged initialization-list change. Existing databases and data were not reset or modified.
    • Verification passed: Secret exists, mfa_service database exists, and all existing SIT workloads remain 1/1 ready.

    The infrastructure prerequisite is now complete. MFA application rollout remains gated on review/merge of the related MFA implementation/configuration PRs.

  6. ramioooz commented on Sep 4, 2026

    @ramioooz
    MemberAuthor

    Release PR is ready for review: digital-bank-java/mfa-service#12

    Verification passed: Maven verify (44 unit, 19 integration), Helm lint, Helm template, and git diff --check. The PR publishes MFA Service 0.0.2 / chart 0.2.0 so the merged persistence and assurance-outbox code can run in SIT.

    Merge order: this release can merge after the already-merged MFA persistence/outbox, infra-sit #30, and config-repo #32 changes. No delay is required after merge. Then build the local image, upgrade SIT, verify Flyway tables and health, and close this task.

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