T91.Server.App 1.0.62

T91.Server.App

OIDC/JWT auth, Swagger, CORS, RabbitMQ, Kafka, REST client, and scope infrastructure for T91 .NET 10 microservices.

Full documentation: GitHub README

Installation

dotnet add package T91.Server.App

Registration

builder.RegisterCurrentScope()       // BaseCurrentScope → HttpCurrentScope (scoped)
       .RegisterOIDC()               // Keycloak-compatible JwtBearer
       .RegisterSwagger()
       .AddCorsPolicy()
       .RegisterKafka()              // IKafkaConnectionRegistry, IKafkaPublisher
       .RegisterRmq()                // IRmqConnectionRegistry, IRmqPublisher
       .RegisterDateTimeConversion() // IDateTimeZoneConverter
       .RegisterCache();             // ICacheService (Redis → Postgres → Null)

builder.Services.AddKafkaConsumer<MyKafkaConsumer>();
builder.Services.AddRmqConsumer<MyRmqConsumer>();

Current Scope

BaseCurrentScope / HttpCurrentScope implement ICurrentScope and ISettableCurrentScope. HTTP requests read context from headers (X-TenantId, X-UserId, X-UserName, Authorization, X-Timezone). Message broker consumers populate it from message headers via ISettableCurrentScope.SetX(...).

Kafka

• IKafkaPublisher.PublishAsync(config, payload, key?, context?, ct) — propagates ICurrentScope as message headers automatically.
• BaseKafkaConsumer<T> — abstract BackgroundService with outer reconnect loop, in-memory retry, and DLQ forwarding to {topic}.dlq. HandleAsync receives a fresh DI scope with tenant context pre-populated.
• Pass context: services.GetRequiredService<ICurrentScope>() when publishing from inside a consumer to forward tenant headers.

RabbitMQ

• IRmqPublisher.PublishAsync(endpoint, payload, context?, ct) — propagates ICurrentScope as AMQP headers.
• BaseRmqConsumer<T> — abstract BackgroundService with reconnect loop, per-message retry via republish, and dead-letter exchange ({queue}.dead.exchange).

REST Client (BaseRestAPI)

Extend BaseRestAPI<TCurrentScope> for typed inter-service HTTP clients. PrepareHeadersAsync auto-forwards X-TenantId, X-UserId, X-UserName, and Authorization on every request. All instances share a single connection pool via a static SocketsHttpHandler.

Config Sections