Stratara.Infrastructure 3.1.1

.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.Infrastructure --version 3.1.1
                    


                    

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


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Stratara.Infrastructure" />
                    


                            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.Infrastructure --version 3.1.1
                    


                    

                
#r "nuget: Stratara.Infrastructure, 3.1.1"
#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.Infrastructure@3.1.1
#: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.Infrastructure&version=3.1.1
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Stratara.Infrastructure&version=3.1.1
                    


                            Install as a Cake Tool

Stratara.Infrastructure

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

Cross-cutting infrastructure plumbing for the Stratara framework — the Tier-C glue that lets downstream apps wire authorization, DI composition, and worker-stack configuration with a single reference.

Contents

  • Authorization decorators over command-outbox dispatch (AuthorizingCommandOutboxDispatcher).
  • DI composition helpers that wire Mediator, Outbox, Identity, and EFCore into a hosted app.
  • Configuration providers and option binders used by the worker stack.

Dependencies

Transitively depends on Stratara.Contracts, Stratara.EventSourcing.EntityFrameworkCore, Stratara.Mediator, Stratara.Outbox.RabbitMQ, Stratara.Sessions, Stratara.Shared.

Behavioural notes

AddSecurity() — IKeyStore registration (since 3.0.11)

AddSecurity() registers Stratara's security stack including the IKeyStore abstraction. The default is a TryAddSingleton<IKeyStore, DummyKeyStore> fallback — but DummyKeyStore since 3.0.11 throws InvalidOperationException in any environment other than Development (whitelist guard to prevent production data exposure from the demo encryption key). Hosts on Staging, QA, UAT, Preview, or any custom environment must register a real IKeyStore implementation before calling AddSecurity():

// Recommended composition root
if (builder.Environment.IsDevelopment())
{
    builder.Services.AddSecurity();   // DummyKeyStore fallback is fine
}
else
{
    builder.Services.AddSingleton<IKeyStore, AzureKeyVaultKeyStore>();  // or AwsKmsKeyStore, HsmKeyStore, ...
    builder.Services.AddSecurity();
}

KeyStoreStartupProbe logs a Warning (event id LogEvents.KeyManagement.DummyKeyStoreActive = 112_001) at host start when the resolved IKeyStore is DummyKeyStore — even in Development — so an accidental dependency on the dummy is loud rather than silent.

Why the change: Before 3.0.11 the guard only blocked IsProduction(). Hosts in any other environment silently encrypted with the world-known constant pass-phrase "StrataraTestKey" baked into the shipping NuGet — a Staging or QA copy of production data could be decrypted by anyone reading the source. The whitelist guard makes this configuration crash-fast at host build instead of allowing silent data exposure.

AddCaching() — Redis registration

AddCaching() used to delegate to builder.AddRedisClient("redis") from Aspire.StackExchange.Redis. After the Aspire-wrapper removal it registers IConnectionMultiplexer directly via ConnectionMultiplexer.Connect(...) from StackExchange.Redis. The method signature is unchanged, but the Aspire-only side-effects are gone:

  • No automatic Redis health check. Add one explicitly with AddHealthChecks().AddRedis(connectionString) (from AspNetCore.HealthChecks.Redis) if your host exposes /health and you want Redis covered.
  • No automatic OpenTelemetry Redis instrumentation. Add OpenTelemetry.Instrumentation.StackExchangeRedis and .AddRedisInstrumentation() to your TracerProviderBuilder if you want Redis spans in your traces.

The connection-string lookup (ConnectionStrings:redis in configuration) is identical to the pre-cleanup behaviour.

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 (2)

Showing the top 2 NuGet packages that depend on Stratara.Infrastructure:

Package Downloads
Stratara.EventSourcing.WorkerDefaults

Worker-host wiring composites for the Stratara event-sourced stack. IHostApplicationBuilder extensions (AddBackendServices, AddCommandWorkerServices, AddEventProjectionWorkerServices, AddSagaWorkerServices, AddOutboxWorkerServices) bundle the per-concern DI calls so each worker host opts in with one line.
Stratara.Testing.EntityFrameworkCore

Spin up the real Stratara event-sourcing write stack (EventSource, aggregation, snapshots, the EF Core write store) against a shared in-memory SQLite database in one call — production code paths, no Postgres, no Docker. Builds on Stratara.Testing's in-memory doubles.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
3.1.7 52 7/1/2026
3.1.6 334 6/22/2026
3.1.5 116 6/22/2026
3.1.4 131 6/15/2026
3.1.3 122 6/10/2026
3.1.2 138 6/5/2026
3.1.1 200 6/1/2026
3.1.0 114 5/30/2026
3.0.23 116 5/28/2026

### Fixed

- **`FileMasterKeyProvider` now rejects a master KEK that is not exactly 32 bytes at startup.**
 The KEK is used directly as an AES-256-GCM key, which accepts only 16/24/32-byte keys. The
 provider previously required merely *at least* 32 bytes, so a longer KEK (for example the
 48-byte output of `openssl rand -base64 48`, a common HKDF master-key recipe) passed both
 construction and the eager `FileKeyStoreStartupProbe`, then threw
 `CryptographicException: Specified key is not a valid size for this algorithm` on the **first**
 key creation at runtime — defeating the purpose of the boot-time probe. The provider now
 validates the decoded length is exactly 32 bytes and fails fast at boot with an actionable
 message (`Generate one with: openssl rand -base64 32`). A 32-byte KEK is unaffected.
- **`EnvelopeFileKeyStore` is now safe for multiple processes sharing one store file** (for
 example several containers bind-mounting the same host directory). Previously a process only
 read the store once at construction, so a data-encryption key created by another process after
 startup was invisible (`GetDataEncryptionKeyAsync` returned `null`, breaking decryption), and
 two processes creating keys concurrently could overwrite each other's keys or mint colliding
 versions for the same scope. Reads now reload from disk on a cache miss (guarded by the file's
 last-write time to avoid reload storms), and every mutation serializes through an exclusive
 cross-process lock file and re-reads the latest on-disk state before writing. A networked file
 system (NFS/SMB) remains unsupported — it guarantees neither atomic rename nor reliable advisory
 locks.

### Added

- **`LogEvents.KeyManagement.KeyStoreReloaded` (112_006)** — debug-level event emitted when the
 file key store reloads its state from disk to pick up keys written by another process.