Skip to main content

LMS Authentication and Tenant Context

Summary​

Training registers HTTP context access and HttpTenantContext. Tenant, tenant key, actor email, user reference, and super-administrator category are derived from request identity/context. Writes call RequireTenantId; EF global filters scope tenant entities and evidence.

No Training service authentication registration, authentication middleware, authorization middleware, endpoint authorization declaration, named policy, role check, employee ownership check, or resource authorization handler was found. Authentication/authorization therefore remain an external trust boundary and Foundation for service-local enforcement.

Correlation middleware is registered. Gateway composition forwards request context through its downstream mechanism. This page intentionally omits claim/header details and any access-circumvention information.

Requires confirmation​

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

Source References​

  • microservices/src/training-service/Program.cs
  • microservices/src/training-service/Application/Common.cs
  • microservices/src/training-service/Infrastructure/TrainingDbContext.cs
  • microservices/src/gateway-api/EssEndpoints.cs

See Also​

Keywords​

  • LMS technical architecture
  • Source-backed implementation

Revision Information​

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