Stratara.Sessions 4.0.2

Prefix Reserved
.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package Stratara.Sessions --version 4.0.2
                    


                    

                
NuGet\Install-Package Stratara.Sessions -Version 4.0.2
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="Stratara.Sessions" Version="4.0.2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Stratara.Sessions" Version="4.0.2" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Stratara.Sessions" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add Stratara.Sessions --version 4.0.2
                    


                    

                
#r "nuget: Stratara.Sessions, 4.0.2"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package Stratara.Sessions@4.0.2
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=Stratara.Sessions&version=4.0.2
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Stratara.Sessions&version=4.0.2
                    


                            Install as a Cake Tool

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-Id header fallback is opt-in via SessionContextOptions.AllowTenantHeader = true (default false). 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 sealed impl of ISessionContextProvider, scoped per request. Writes Activity tags (correlation.id, causation.id, tenant.id, user.id) automatically on Set / Clear.
  • SessionContextMiddleware — ASP.NET Core middleware that extracts tenant + user from ClaimTypes.NameIdentifier + stratara:tenant_id claim (with optional X-Tenant-Id header fallback gated by SessionContextOptions.AllowTenantHeader) and constructs a SessionContext with Actor=Subject (the default UserPlatform case).
  • SessionContextOptions — configuration (SessionContext section) controlling the header fallback gate. Bind via services.Configure<SessionContextOptions>(...) or services.AddOptions<SessionContextOptions>().Bind(...).
  • StrataraClaimTypes — claim-name constants (stratara:tenant_id).
  • DefaultTenantIdentifier — sentinel Guid used when no tenant claim or header is present (typically anonymous / system flows).
  • AddSessionContext() DI extension — registers the concrete provider as a scoped service against ISessionContextProvider.

Adopting the Actor/Subject model

For most operations Actor equals the data-owner Subject — a user acts on their own tenant's data. The split only diverges 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 — for ISessionContextProvider.
  • Stratara.Contracts — for the SessionContext record (wire-level).
  • Stratara.Diagnostics — for ApplicationDiagnostics activity tags.
  • Microsoft.AspNetCore.Http.Abstractions — for HttpContext / RequestDelegate.
  • Microsoft.Extensions.DependencyInjection.Abstractions.
  • OpenTelemetry.Api.
Product 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

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.0.4 248 9/14/2026
4.0.3 301 9/3/2026
4.0.2 732 9/3/2026
4.0.1 274 9/2/2026
4.0.0 659 8/31/2026
4.0.0-preview.1 116 8/31/2026
3.4.0 307 8/28/2026
3.3.0 461 8/25/2026
3.2.3 281 8/22/2026
3.2.2 852 8/14/2026
3.2.1 858 8/2/2026
3.2.0 247 7/18/2026
3.1.7 514 7/1/2026
3.1.6 674 6/22/2026
3.1.5 260 6/22/2026
3.1.4 2,068 6/15/2026
3.1.3 261 6/10/2026
3.1.2 271 6/5/2026
3.1.1 945 6/1/2026
3.1.0 245 5/30/2026
Loading failed

Two operational fixes, both found while a consumer rolled out bus-envelope signing and reasoned
about rebuilding its read models: a projection replay now survives a passing failure, and an
integrity failure says whether the signature was absent or wrong. Additive on every published
surface.

### Added

- **A projection replay retries a failing batch before it gives up.** Each batch — the read from
 the event store and the application of its entries — now runs under a new named policy,
 `ResilienceNames.ProjectionReplayBatch`: five attempts in all, exponential backoff from one second
 with jitter between them, any exception except cancellation. A read-store timeout or a
 dropped connection mid-rebuild no longer ends the replay; a failure that persists through every
 attempt ends it exactly as before, with the same failure record. A retried batch is applied
 again from its first entry in a fresh scope, which relies on the guarantee projections already
 give under at-least-once delivery: a second application converges (see *Write handlers that
 converge rather than accumulate* in the projection guide). Each failed attempt logs a new
 warning, `104_011`. `AddResiliencePipelines` registers six policies rather than five. Nothing
 about truncation, ordering, progress, the failure record or the lease changes.

### Changed

- **An integrity failure now says whether the signature was absent or wrong, and the existing
 warning and error ids fire only for a signature that is present and does not verify.** An
 unsigned envelope — what every not-yet-restarted publisher emits during a `Permissive` roll —
 was logged as *"signature mismatch"* under the same id as a key mismatch or tampering, so an
 operator could not tell a rolling restart from an attack without correlating host start times.
 Four new event ids carry the unsigned case: `105_004` (command, permissive), `111_004` (event
 bundle, permissive), `105_105` (command, strict) and `111_105` (event bundle, strict). The
 existing `105_003`, `111_003`, `105_104` and `111_104` keep their numbers and their level but
 now mean a present signature that did not verify; an alert keyed on one of them goes quiet
 during a roll instead of firing for every unsigned message. Strict-mode rejections name the
 case in their exception message. `BusEnvelopeIntegrityVerifier.Verify` gains an overload with
 `out BusEnvelopeIntegrityFailure` (`None`, `Absent`, `Invalid`); the existing overload and the
 `BusEnvelopeIntegrityResult` values are unchanged. An absent signature no longer reaches the
 signer, which already answered `false` for it.