Skip to content

fix: align transfer gateway scope - #27

Merged
ramioooz merged 1 commit into
mainfrom
fix/263-transfer-scope
Sep 9, 2026
Merged

ramioooz merged 1 commit into
mainfrom
fix/263-transfer-scope

Conversation

@ramioooz

@ramioooz ramioooz commented Sep 9, 2026

Copy link
Copy Markdown
Member

Summary

  • require the established transfer.internal authority for transfer workflow routes
  • add one Gateway security regression check for canonical transfer scope admission
  • preserve denial for tokens without the required scope

Root cause

The Gateway required transaction.internal, but Auth configuration, Transaction Service authorization, and the documented transfer contract use transfer.internal. Authenticated transfer requests were rejected with HTTP 403 before reaching Transaction Service.

Verification

  • ./mvnw --batch-mode --no-transfer-progress -Dtest=GatewaySecurityIntegrationTests test
  • ./mvnw --batch-mode --no-transfer-progress verify
  • both passed with host networking enabled for Netty integration tests

Tracking

This is a normal, non-draft PR. No CI jobs or redundant test suites were added.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BUG: Align Gateway transfer authorization with the transfer scope contract

1 participant