Leave API Authentication and Context

Summary

Bearer identity and trusted gateway context supply tenant, actor, user, employee, and role information, but final route-level extracted-service authorization parity requires confirmation.

Audience

Developers, QA, architects, security, support, and implementation partners.

Overview

Mutations call the tenant requirement and missing tenant is translated to a handled 400 response. Queries rely on global tenant filters and can behave differently when context is absent; clients must always send valid context.

Compatibility monolith controllers require authentication and apply self/team/approver, tenant-wide, or administrator checks depending on operation. Extracted Minimal API declarations do not uniformly attach confirmed per-route authorization metadata; documentation therefore states authentication expected; authorization Requires confirmation for direct operations.

Workflow callback is Internal and must arrive through an approved trusted service boundary. Signing details, token values, exact forwarding headers, privileged internals, and non-production mechanisms are excluded.

Source References

• microservices/src/leave-service/Program.cs
• microservices/src/leave-service/Infrastructure/Persistence.cs
• Controllers/LeaveRequestsController.cs
• microservices/src/gateway-api/Program.cs

Related Articles

• Leave API
• Response and error model

See Also

• Leave technical documentation
• Leave business documentation

Keywords

• Leave API
• Leave API Authentication and Context
• Integration

Revision Information

• Status: Draft
• Last reviewed: 2026-07-15
• Review cycle: Quarterly