LMS Gateway Integration

Summary

Confirmed Gateway behavior is employee self-service proxy/aggregation to the Training enrollment read. The frontend also calls canonical Training routes through its API abstraction; a distinct LMS compatibility route or shadow path was not found.

Gateway code forwards request context through its downstream client path and provides degraded module behavior in aggregation. Exact native reverse-proxy ownership outside ESS, route authorization policy, self-only filtering, retry governance, and cutover behavior require confirmation. No legacy LMS adapter is present.

Requires confirmation

Fine-grained authorization, production ownership, operational governance, and future architectural boundaries require confirmation where not implemented.

Source References

• microservices/src/gateway-api/EssEndpoints.cs
• microservices/src/training-service/Api/TrainingEndpoints.cs
• UI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsx
• UI/salary-ui/apps/client-hrms-portal/src/pages/hr/TalentAdminPages.tsx

Related Articles

• LMS technical documentation
• LMS business documentation

See Also

• Technical limitations
• Technical source map

Keywords

• LMS technical architecture
• Source-backed implementation

Revision Information

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