Asset Authentication and Tenant Context
Security context
Bearer authentication is registered for multiple accepted issuer/key families and uses email and role claims for principal mapping. Authorization services and middleware are registered. However, direct and compatibility endpoint groups do not call authorization requirements or role policies, so authentication is not enforced by route metadata.
HttpTenantContext resolves tenant key/identifier, super-administrator role, actor email, user reference, and labor reference from claims or forwarded request headers. Commands require a tenant; missing tenant becomes a client error. Actor uses email with a system fallback. DbContext query filters apply tenant isolation to assets and owned evidence, with a super-administrator bypass.
Header trust, gateway-to-service authenticity, resource ownership, callback caller identity, document authorization, and fine-grained roles are not enforced locally. This page intentionally omits signing/configuration values.
Requires confirmation
Production ownership, authorization governance, operational policy, and future architecture require confirmation where the source does not enforce them.
Source References
microservices/src/asset-service/Program.csmicroservices/src/asset-service/Infrastructure/Persistence.csmicroservices/src/asset-service/Infrastructure/AssetDbContext.cs