Skip to content

TASK: Inject SIT Auth fixture username through Helm Secret #243

Closed

Description

@ramioooz

Objective

Make the SIT Auth Service fixture usable for the controlled MFA step-up acceptance flow.

Scope

  • Add a configurable fixture username Secret key to the Auth Service Helm values.
  • Inject AUTH_FIXTURE_USERNAME from the existing auth-service Secret.
  • Preserve the existing secret-only credential model; do not add raw passwords or committed credentials.
  • Keep the current runtime profile, JWT secret, password-hash, database, and security boundaries unchanged.

Acceptance Criteria

  • Helm renders AUTH_FIXTURE_USERNAME from the configured Secret key when secrets are enabled.
  • Existing SIT Secret key names remain configurable.
  • Helm lint and template validation pass.
  • Auth Service starts with a nonblank fixture username in SIT.
  • The controlled acceptance flow for .github#208 can perform login without exposing credential values.

Verification

  • Inspect rendered deployment for the environment variable and Secret reference without printing Secret values.
  • Run the existing Auth Service Maven, Helm, and diff checks.
  • Record runtime evidence only after the parent task's controlled SIT acceptance is executed.

Activity

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

    @ramioooz
    MemberAuthor

    Implementation PR: digital-bank-java/auth-service#11

    The Auth Service Helm chart now injects AUTH_FIXTURE_USERNAME from the configured auth-service Secret key fixture-username and documents all required key names. Local Maven, Helm, and diff checks passed. The existing SIT Secret was updated with the documented synthetic fixture username key without reading or changing existing secret values. Awaiting PR merge before rollout and parent task acceptance.

  4. ramioooz commented on Sep 6, 2026

    @ramioooz
    MemberAuthor

    Completion evidence (2026-09-06)

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