Skip to content

TASK: Document and provision shared SIT Auth JWT secret #192

Closed

Description

@ramioooz

Parent: #191
Sprint parent: #21

Objective

Provide the controlled local SIT secret delivery needed by Auth Service and Transaction Service to use the same HMAC JWT contract.

Scope

  • Document creation of auth-service-secrets in digital-bank-sit without committing credentials.
  • Use the same Secret name and jwt-secret key for Auth Service and Transaction Service.
  • Keep generated values synthetic and local-SIT-only.
  • Document safe verification without printing the secret.
  • Record that UAT and PROD must use AWS Secrets Manager with External Secrets or an equivalent controlled integration.

Acceptance criteria

  • A tracked infra runbook contains the Secret creation and verification procedure.
  • No secret value appears in Git, Helm values, issue bodies, logs, or PR descriptions.
  • Auth and Transaction Helm charts reference the same Secret contract.
  • The procedure supports a clean SIT rollout after the related PRs are merged.

This task is a prerequisite for end-to-end Auth login and authorized Transaction Service verification.

Activity

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

    @ramioooz
    MemberAuthor

    Implementation status

    Both PRs are non-draft and contain no secret values. The runbook PR should be merged before treating this Task as complete; the handoff PR may merge independently.

  4. ramioooz commented on Sep 3, 2026

    @ramioooz
    MemberAuthor

    The local SIT Secret prerequisite has been provisioned and verified without exposing its value. Task completion remains pending infra-sit#28 merge and the subsequent Auth/Transaction rollout verification.

  5. ramioooz commented on Sep 3, 2026

    @ramioooz
    MemberAuthor

    Implementation is ready in .github#201. The PR adds the tracked SIT secret runbook, safe verification/rotation guidance, local-SIT links, and the deferred AWS Secrets Manager direction. It is non-draft and must be reviewed before closing 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