Skip to content

BUG: Align Gateway transfer authorization with the transfer scope contract #263

Closed
digital-bank-java/api-gateway
#27

Description

@ramioooz

Problem

The API Gateway currently requires transaction.internal for /internal/v1/transfer-workflows, while Auth, Transaction Service, and the documented transfer contract use transfer.internal. Authenticated transfer requests therefore receive 403 before the workflow reaches Transaction Service.

Scope

  • Require the established transfer.internal scope at the Gateway transfer route.
  • Preserve Transaction Service subject allowlisting and downstream authorization.
  • Add one load-bearing regression check for the scope contract.
  • Verify the corrected route in local SIT through the approved synthetic transfer fixture.

Acceptance Criteria

  • A token with transfer.internal can reach the governed transfer route.
  • A token without transfer.internal remains denied.
  • No public balance mutation route or alternate scope is introduced.
  • The change is linked to the controlled SIT acceptance fixture and the transfer saga story.

Parent: TASK: Provision controlled SIT transfer acceptance fixture (#261)
Sprint: Sprint 3 - Internal Transfers and Event Consistency
Assignee: ramioooz

Activity

  1. added theissue type on Sep 9, 2026
  2. ramioooz commented on Sep 9, 2026

    @ramioooz
    MemberAuthor

    Root cause confirmed in local SIT on 2026-09-09: the Auth fixture login succeeded after the runner readiness fix, but the transfer received HTTP 403 at the API Gateway. Live configuration and code showed Gateway required SCOPE_transaction.internal while Auth, Transaction Service, and the transfer documentation contract use transfer.internal.

    Implementation: api-gateway#27 changes the Gateway requirement to SCOPE_transfer.internal and adds one focused security regression check. ./mvnw verify passed with 21 tests.

    The acceptance runner remains uncompleted until #27 is merged and the feature image/fixture can be rerun. No secrets or database rows were exposed or manually changed.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions