Authentication and Access
Summary
Attendance navigation is absent, a protected route redirects, or an Attendance request returns 401/403.
Audience
Employees or administrators affected by the scenario, first-line support, QA, service owners, and operations.
Symptoms
- Attendance navigation is absent, a protected route redirects, or an Attendance request returns 401/403.
Scope
Authentication and authorization only.
Likely causes
Missing/expired authentication, missing tenant context, unavailable feature/route permission, or transitional service-policy mapping.
Cause
The confirmed cause categories are listed under Likely causes above; determine the applicable category from sanitized evidence before taking action.
Safe diagnostic steps
- Confirm sign-in state, tenant selection, route rule, response category, and correlation identifier. Compare the attempted capability with the permissions reference.
- Preserve tenant isolation and redact personal or security-sensitive data.
- Do not use direct database changes, authorization bypasses, or ad hoc broker operations.
Safe resolution
Re-authenticate when appropriate; select the authorized tenant; request approved access from the identity owner. Do not change claims or bypass guards.
Resolution
Apply only the Safe resolution described above and remain within the documented ownership boundary.
Validation
Reload the protected route and repeat only the authorized read/action.
Evidence to collect
Route, 401 versus 403, timestamp, sanitized identity/tenant context, and correlation identifier.
Escalation
Identity/security for authentication or grants; Gateway/Attendance owner when valid access is rejected.
Related docs
Related Articles
Source References
UI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsxmicroservices/src/attendance-service/Api/Endpoints.cs
See Also
Keywords
- Attendance
- Troubleshooting
- Authentication and Access
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly