Stratara.Sessions 3.2.3

.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 3.2.3
                    


                    

                
NuGet\Install-Package Stratara.Sessions -Version 3.2.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.2.3" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Stratara.Sessions" Version="3.2.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.2.3
                    


                    

                
#r "nuget: Stratara.Sessions, 3.2.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.2.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.2.3
                    


                            Install as a Cake Addin
                        

                    

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


                            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
3.3.0 107 8/25/2026
3.2.3 216 8/22/2026
3.2.2 789 8/14/2026
3.2.1 841 8/2/2026
3.2.0 239 7/18/2026
3.1.7 330 7/1/2026
3.1.6 667 6/22/2026
3.1.5 251 6/22/2026
3.1.4 2,062 6/15/2026
3.1.3 254 6/10/2026
3.1.2 266 6/5/2026
3.1.1 937 6/1/2026
3.1.0 237 5/30/2026
3.0.23 232 5/28/2026

Three correctness fixes, all of the same kind: behaviour that failed by succeeding. A pipeline
behaviour registered twice ran twice and nothing said so; a closed generic type name normalized to a
malformed key that two different types could share, and the loser of that collision was discarded
silently; and a heavy command republished from the outbox left its lane whenever its type could not
be resolved. None produced an error, and no test covered any of them. They were found by reading the
code against the specification rather than by a failure report.

### Fixed

- **A pipeline behaviour registered twice now installs once.** Every behaviour registrar used a
 plain scoped registration, so a host that called one twice — the ordinary result of composing two
 service bundles that each set up their own slice of the framework — installed the stage twice and
 ran it twice per request. None of the three consequences was benign: every validator ran twice
 against every request, so a validator with a side effect (a uniqueness check against the database)
 performed it twice; the tenant guard ran twice, the second time against a second options instance
 that could disagree with the first; and two nested resilience pipelines multiplied rather than
 added, turning a configured budget of four attempts into sixteen. `AddStrataraValidation`,
 `AddStrataraTenantIsolation`, `AddStrataraResilienceBehavior`, `AddCommandAuditing` and the
 `AddPipelineBehavior` / `AddPipelineBehaviorWithResult` primitives are now idempotent per behaviour
 type. Registering two *different* behaviours is unaffected.
- **A closed generic type name now normalizes correctly.** Resolving a recorded type name is meant to
 ignore the assembly version and match on the type name and assembly name alone. For a closed
 generic it did neither: the name was truncated at its second comma, which for a generic falls
 *inside* the type-argument brackets, so the outer assembly name was dropped and the key became a
 malformed fragment. Two closed generics that differed only in the assembly that declared them
 collapsed onto one key, and the second registration was then silently discarded — an event
 upcaster could match the wrong source type, and a type a host believed it had registered was
 unresolvable. Names are now parsed rather than counted, and each type argument is reduced the same
 way as the outer name, so upgrading the *payload's* assembly no longer strands rows either.
- **A heavy command republished from the outbox stays in the heavy lane.** When a stored command's
 recorded type could not be resolved in the process draining the outbox, republication fell back to
 the shared command topic regardless of the lane the command belonged to. Depending on how the lanes
 are deployed, the command was then either dead-lettered by the interactive worker or executed on
 the interactive lane — the starvation the separate lane exists to prevent. The lane is now recorded
 on the envelope when the command is enqueued, so republication no longer depends on resolving the
 type.

### Changed

- **Registering two different types under one recorded name now fails.** The trusted-type resolver
 previously kept the first and discarded the second without a word, which is indistinguishable from
 a registration that never happened: the type simply fails to resolve later, when a stored row is
 read. `ITrustedTypeResolver.Register` now throws, naming both types. Registering the same type
 again remains a no-op. Reaching this requires two distinct types sharing a full type name *and* a
 simple assembly name in one process.
- **`TenantIsolationOptions` follows the options pattern.** The mode can now be bound from
 configuration with `Configure<TenantIsolationOptions>(section)` in addition to the
 `AddStrataraTenantIsolation(o => ...)` callback, and a second call to the registrar no longer
 leaves a conflicting second options instance behind. `Stratara.Mediator` therefore takes a
 dependency on `Microsoft.Extensions.Options`.

### Added

- **`CommandEnvelope.Heavy`** records whether a command declared itself long-running when it was
 enqueued. Optional and defaulting to `false`, which is how an envelope written by an earlier
 version deserializes; the signed canonical form is unchanged, so existing signatures still verify.