Helpdesk Authentication and Authorization
Audience
Developers, security, QA, support and architects.
Summary
The Helpdesk Service reads claims and forwarded headers through HttpTenantContext, but its reviewed startup does not register or invoke authentication/authorization middleware and its route groups do not require policies.
Reference Content
Tenant, user, email and super-administrator role can be derived from request identity/context. Frontend navigation uses audience, role aliases and feature/permission values; protected routes provide broader client-side access checks. These client controls are presentation controls and do not establish service authorization.
The gateway forwards request context to downstream services, but static source does not prove a trusted network boundary or authenticated principal at Helpdesk.
Requires confirmation
End-to-end authentication, trusted header handling, route policies, role/permission enforcement, service-to-service identity and super-administrator governance require confirmation.
Source References
microservices/src/helpdesk-service/Program.csmicroservices/src/helpdesk-service/Application/Common.csmicroservices/src/gateway-api/Program.csUI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsxUI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsx
Related Articles
See Also
Keywords
Authentication, authorization, claims, forwarded headers, route policy.
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20