Stratara.Sessions 3.1.3

dotnet add package Stratara.Sessions --version 3.1.3
                    
NuGet\Install-Package Stratara.Sessions -Version 3.1.3
                    
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="3.1.3" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Stratara.Sessions" Version="3.1.3" />
                    
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 3.1.3
                    
#r "nuget: Stratara.Sessions, 3.1.3"
                    
#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@3.1.3
                    
#: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=3.1.3
                    
Install as a Cake Addin
#tool nuget:?package=Stratara.Sessions&version=3.1.3
                    
Install as a Cake Tool

Stratara.Sessions

License: FSL-1.1-MIT (Functional Source License — source-available; converts to MIT after 2 years). Not OSI-approved OSS.

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

  • SessionContextProviderinternal 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 outbox / saga / projection / messaging, 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
3.1.3 173 6/10/2026
3.1.2 244 6/5/2026
3.1.1 754 6/1/2026
3.1.0 219 5/30/2026
3.0.23 215 5/28/2026

### Added

- **Mediator tenant-isolation behavior** (`Stratara.Mediator`) — `AddStrataraTenantIsolation()`
 registers a pipeline behavior that enforces tenant isolation at the mediator entrance, before the
 handler runs, for any request that opts in via the new `ITenantScopedRequest` marker
 (`Stratara.Abstractions.Multitenancy`). The behavior compares the request's `TenantId` (data owner)
 against the ambient session's data-owner tenant and rejects a mismatch with the new
 `TenantAccessDeniedException` (translated to HTTP 403 on ASP.NET hosts). `TenantIsolationMode.Default`
 enforces only the subject match (privileged cross-tenant operations pass when the endpoint promoted
 the session subject to the target); `TenantIsolationMode.Strict` additionally routes every
 cross-tenant operation through the new `ICrossTenantAuthorizer`, whose shipped default denies all
 cross-tenant access until a consumer registers its own authorizer. Complements the existing
 database-side `ApplyGlobalTenantQueryFilters` with a command-/query-entrance guard. New log-event
 IDs `114_101`/`114_102`/`114_003` in `Stratara.Diagnostics`.
- **`Stratara.Abstractions.Persistence.ConcurrencyConflictException`** — provider-agnostic
 wrapper for an optimistic-concurrency conflict detected during commit. Allows framework-level
 code in `Stratara.Projections` (and any consumer outside the `EntityFrameworkCore` package) to
 react to concurrency without taking an EF Core dependency. EF Core's `DbUpdateConcurrencyException`
 (and provider equivalents) flow through this type.

### Changed

- **`EfTransaction.SaveChangesAsync`** (in `Stratara.EventSourcing.EntityFrameworkCore`) now
 wraps `DbUpdateConcurrencyException` thrown by EF Core in the new
 `ConcurrencyConflictException`. PostgreSQL unique-violation paths remain on `DbUpdateException`
 (different semantics — duplicate-key on insert vs. stale-row on update/delete).
- **`EventSource.SaveChangesAsync`** (write-side append flow) extends its concurrency-handling
 catch to the new exception type so the existing append-conflict recovery path keeps working
 after the wrap. Behaviour for both EF concurrency conflicts and PostgreSQL unique violations
 is unchanged.

### Fixed

- **`TenantProjection` no longer aborts the event bundle on a parallel delete race.** The two
 delete handlers (`TenantDeleted`, `CustomerTenantsDeleted`) now swallow
 `ConcurrencyConflictException` silently — a missing row is the desired end-state of a delete.
 Before this fix, a consumer-side customer-delete cascade saga that emits both
 `CustomerTenantsDeleted` and a follow-up `TenantDeleted` for the same tenants would race the
 two parallel projection bundles on the same `TenantView` row; the loser threw
 `DbUpdateConcurrencyException` out of `SaveChangesAsync`, which propagated through
 `ProjectionWorker` and caused `RabbitMqBus` to roll back the entire bundle — including
 sibling projections that had already committed. Update handlers (rename / activate /
 deactivate / locale / customer-assigned) keep their current behaviour: a concurrency failure
 there is a real race that propagates.