You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
TASK: Route security and transaction workflows through API Gateway in SIT #202
Expose the implemented internal transfer and security workflow APIs through the SIT API Gateway so normal integration testing uses one gateway entry point.
Scope
Route Auth Service login and logout APIs.
Route MFA enrollment and challenge APIs.
Route internal transfer workflow APIs.
Route internal payment instruction APIs.
Add the corresponding service OpenAPI definitions to centralized Swagger UI.
Add health routes for the newly deployed services.
Preserve downstream authorization and keep internal payment/transfer APIs out of public business documentation.
Acceptance Criteria
SIT gateway routes resolve to stable Kubernetes Service DNS names.
Authorization headers are forwarded to downstream services.
Centralized Swagger UI lists the available service contracts with their intended internal/public classification.
No credentials, tokens, or production endpoints are committed.
Config Server lookup, Helm rollout, and representative gateway requests are documented.
Related work
Auth and MFA workflow stories: .github#45, .github#49.
Payment and notification capability: .github#98.
Existing transaction workflow: .github#54.
This is configuration-only; application unit tests are not required.
Activity