Skip to main content

Employee Authentication and Access Troubleshooting

Summary​

Client route guard, navigation visibility, monolith access scope, and extracted-service authentication policies.

Audience​

  • HR administrators, support engineers, developers, QA engineers, and DevOps engineers

Symptoms​

Employee menu is absent, route shows Unauthorized, login redirection occurs, or API returns unauthenticated/forbidden.

Scope​

Client route guard, navigation visibility, monolith access scope, and extracted-service authentication policies.

Cause​

Likely causes​

  • Missing/expired tenant session or forced password change
  • Workforce or Employee navigation permission evidence absent
  • API access scope is narrower than UI expectation
  • Gateway destination has different authorization behavior

Safe diagnostic steps​

  1. Confirm whether the user is authenticated in the correct tenant without collecting the token
  2. Check menu visibility versus direct route behavior and record the safe status category
  3. Identify monolith or extracted route source; compare frontend guard with API enforcement

Resolution​

Safe resolution​

  • Reauthenticate through the approved login flow
  • Ask identity/access owners to review assigned roles/features; do not add permissions as a troubleshooting shortcut
  • Escalate UI/API enforcement mismatches

Validation​

The approved user reaches the route and can perform only source-authorized read/mutation scope.

Evidence to collect​

User role/feature names safe to share, tenant-safe identifier, route, status, correlation identifier, route source.

Escalation​

Identity/security owner for session/claims; Employee owner for API policy; gateway owner for route mismatch.

Source References​

  • UI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsx
  • Controllers/LaborController.cs
  • microservices/src/employee-service/Program.cs

See Also​

Keywords​

  • Employee troubleshooting
  • Authentication and Access
  • safe diagnostics

Revision Information​

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