Stratara.Sessions
4.4.8
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Sessions --version 4.4.8
NuGet\Install-Package Stratara.Sessions -Version 4.4.8
<PackageReference Include="Stratara.Sessions" Version="4.4.8" />
<PackageVersion Include="Stratara.Sessions" Version="4.4.8" />
<PackageReference Include="Stratara.Sessions" />
paket add Stratara.Sessions --version 4.4.8
#r "nuget: Stratara.Sessions, 4.4.8"
#:package Stratara.Sessions@4.4.8
#addin nuget:?package=Stratara.Sessions&version=4.4.8
#tool nuget:?package=Stratara.Sessions&version=4.4.8
Stratara.Sessions
Derived. The behaviour described here is specified under
openspec/specs/. Those specifications are the source; this page explains and illustrates them.
License: MIT.
Concrete session-context provider + ASP.NET Core middleware for Stratara's Actor/Subject session model. Reads tenant + user identity from JWT claims (with optional X-Tenant-Id / X-Client-Id header fallbacks), populates the ambient ISessionContextProvider, and exposes the Actor/Subject pair to every request.
Since 3.0.10: the
X-Tenant-Idheader fallback is opt-in viaSessionContextOptions.AllowTenantHeader = true(defaultfalse). Without the gate, any authenticated principal could pick the tenant their request operated against in hosts whose JWT does not carry the tenant claim. Embed the tenant id in the JWT claim set, or opt in explicitly when an upstream platform-admin role check guards the header.
Quick start
// Program.cs / Startup.cs
builder.Services.AddSessionContext();
// In the middleware pipeline:
app.UseMiddleware<SessionContextMiddleware>();
Then resolve in any scoped service:
public sealed class SomeHandler(ISessionContextProvider sessionContextProvider)
{
public async Task HandleAsync(...) {
var session = sessionContextProvider.Current
?? throw new InvalidOperationException("Session context not set");
// session.TenantId = Subject (data owner) — used for filtering / encryption AAD
// session.UserId = Subject user (nullable)
// session.ActorTenantId = Actor (who triggered) — audit trail
// session.ActorUserId = Actor user — audit trail
}
}
What's in the box
SessionContextProvider—internal sealedimpl ofISessionContextProvider, scoped per request. Writes Activity tags (correlation.id,causation.id,tenant.id,user.id) automatically onSet/Clear.SessionContextMiddleware— ASP.NET Core middleware that extracts tenant + user fromClaimTypes.NameIdentifier+stratara:tenant_idclaim (with optionalX-Tenant-Idheader fallback gated bySessionContextOptions.AllowTenantHeader) and constructs aSessionContextwhose actor tenant and data-owner tenant are the claimed tenant, whose actor user is the claimed user, and whose data-owner user is left unset. It stays unset on purpose: the scope a protected field is encrypted under follows the data owner, so filling in the user would move every protected field written from a request to a per-user scope.SessionContextOptions— configuration controlling the header fallback gate.AddSessionContext()reads it from theSessionContextsection of the host's configuration;services.Configure<SessionContextOptions>(...)after that call takes precedence. Since 4.2.0 the section is read — an"AllowTenantHeader": truethat did nothing before turns the fallback on.StrataraClaimTypes— claim-name constants (stratara:tenant_id).DefaultTenantIdentifier— sentinelGuidused when no tenant claim or header is present (typically anonymous / system flows).AddSessionContext()DI extension — registers the concrete provider as a scoped service againstISessionContextProvider.
Adopting the Actor/Subject model
For most operations the actor's tenant is the data-owner tenant — a user acts on their own tenant's data — while the data-owner user stays unset unless the application sets it. The tenants only diverge for:
- PlatformAdmin cross-tenant operations (Subject = customer tenant, Actor = admin tenant)
- Anonymous endpoints (Actor =
Guid.Empty, Subject = the just-minted tenant) - System / saga flows (Actor =
SessionContext.SystemActorTenantId/SystemActorUserId)
Consumers that reject ambient context (libraries that prefer explicit TenantId parameters everywhere) do not need to take this package — Stratara.Mediator and the rest of the framework work without an ISessionContextProvider registered as long as no path requires it.
Dependencies
Stratara.Abstractions— forISessionContextProvider.Stratara.Contracts— for theSessionContextrecord (wire-level).Stratara.Diagnostics— forApplicationDiagnosticsactivity tags.Microsoft.AspNetCore.Http.Abstractions— forHttpContext/RequestDelegate.Microsoft.Extensions.DependencyInjection.Abstractions.OpenTelemetry.Api.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Microsoft.AspNetCore.Http.Abstractions (>= 2.3.13)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.13)
- Microsoft.Extensions.Options (>= 10.0.13)
- Microsoft.Extensions.Options.ConfigurationExtensions (>= 10.0.13)
- OpenTelemetry.Api (>= 1.20.1)
- Stratara.Abstractions (>= 4.4.8)
- Stratara.Contracts (>= 4.4.8)
- Stratara.Diagnostics (>= 4.4.8)
NuGet packages (3)
Showing the top 3 NuGet packages that depend on Stratara.Sessions:
| Package | Downloads |
|---|---|
|
Stratara.Shared
Umbrella package for the Stratara framework — source-generated logger extensions for command flows, domain-event helpers, merge primitives, and the Tier-A/B abstractions surface re-exported as one transitive bundle. |
|
|
Stratara.Outbox.RabbitMQ
Outbox-pattern command and event dispatch for the Stratara event-sourced stack — RabbitMQ IMessageBus implementation, retry worker, mediator command worker, and Redis-coordinated projection-replay state. Azure Service Bus support ships as the sibling Stratara.Outbox.AzureServiceBus package. |
|
|
Stratara.Infrastructure
Infrastructure glue for the Stratara framework — authorization decorators, configuration providers, and DI composition helpers that wire Mediator, Outbox, Identity, and EF Core into a hosted app. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.8.0 | 384 | 11/6/2026 |
| 4.7.1 | 337 | 11/5/2026 |
| 4.7.0 | 739 | 10/30/2026 |
| 4.6.1 | 272 | 10/29/2026 |
| 4.6.0 | 355 | 10/28/2026 |
| 4.5.0 | 425 | 10/28/2026 |
| 4.4.10 | 366 | 10/26/2026 |
| 4.4.9 | 269 | 10/26/2026 |
| 4.4.8 | 410 | 10/24/2026 |
| 4.4.7 | 273 | 10/23/2026 |
| 4.4.6 | 394 | 10/22/2026 |
| 4.4.5 | 800 | 10/14/2026 |
| 4.4.4 | 532 | 10/10/2026 |
| 4.4.3 | 278 | 10/10/2026 |
| 4.4.2 | 631 | 10/2/2026 |
| 4.4.1 | 580 | 9/29/2026 |
| 4.4.0 | 314 | 9/27/2026 |
| 4.3.1 | 372 | 9/25/2026 |
| 4.3.0 | 555 | 9/23/2026 |
| 4.2.0 | 332 | 9/18/2026 |
A fix for hosts on the Orleans execution model. A store reader that catches up a large backlog and a singleton
work that runs long now answer their keep-alive, so neither leaves reminder errors in the silo's log. A silo that
joins while a singleton work runs long on another silo no longer fails its start. No API change, no schema change
and no migration.
### Fixed
- **A busy store reader or singleton work answers its keep-alive.** On the Orleans execution model, a projection or
saga reader that caught up a backlog for longer than the runtime's response timeout made its keep-alive tick wait
behind the catch-up, and Orleans logged `Could not deliver reminder tick` at Error, once per partition and
keep-alive period. A singleton work whose run outlasted the timeout did the same. Nothing was lost, but a large
catch-up left dozens of errors on the silo. The keep-alive and the poll now start a catch-up where none is
running and do not wait for it. A partition is still read by one catch-up at a time, and a commit during a
catch-up is still applied by it. A singleton work's keep-alive interleaves with its run, and runs still never
overlap.
- **A silo starts while a singleton work runs long.** A silo that started while a singleton work it registers ran
longer than the response timeout on another silo waited for that run in its own start. The start then failed
with a `TimeoutException`. The call a starting silo makes to each singleton work and store reader now
interleaves, so the start goes on.
- *Operate the Orleans execution model* says that a durable timer whose handler outlasts the response timeout
still makes Orleans log `Could not deliver reminder tick` for that tick, and that the line says nothing about
the timer. It also says that, outside a deploy, the line now points to an unreachable store reader or singleton
work rather than a busy one.