Stratara.EventSourcing.Pipeline.CommandAudit
4.7.0
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.EventSourcing.Pipeline.CommandAudit --version 4.7.0
NuGet\Install-Package Stratara.EventSourcing.Pipeline.CommandAudit -Version 4.7.0
<PackageReference Include="Stratara.EventSourcing.Pipeline.CommandAudit" Version="4.7.0" />
<PackageVersion Include="Stratara.EventSourcing.Pipeline.CommandAudit" Version="4.7.0" />
<PackageReference Include="Stratara.EventSourcing.Pipeline.CommandAudit" />
paket add Stratara.EventSourcing.Pipeline.CommandAudit --version 4.7.0
#r "nuget: Stratara.EventSourcing.Pipeline.CommandAudit, 4.7.0"
#:package Stratara.EventSourcing.Pipeline.CommandAudit@4.7.0
#addin nuget:?package=Stratara.EventSourcing.Pipeline.CommandAudit&version=4.7.0
#tool nuget:?package=Stratara.EventSourcing.Pipeline.CommandAudit&version=4.7.0
Stratara.EventSourcing.Pipeline.CommandAudit
Derived. The behaviour described here is specified under
openspec/specs/. Those specifications are the source; this page explains and illustrates them.
License: MIT.
Mediator pipeline behavior that records an audit row for every dispatched command in the Stratara event-sourced stack. Both arities are provided so consumers can register a single behavior pair and have it apply to all command shapes.
What's in the box
| Type | Purpose |
|---|---|
AddCommandAuditing() |
The package's public surface — registers both behavior arities in one call. |
CommandAuditBehavior<TRequest> (internal) |
Runs the audit-write step before delegating to next() for IRequest (commands without result). |
CommandAuditBehavior<TRequest, TResult> (internal) |
Same, for IRequest<TResult> (commands with result + queries). Only records when the request also implements ICommandBase — queries flow through untouched. |
CommandAuditWriter (internal) |
Opens a transaction on IWriteUnitOfWork, writes via ICommandAuditRepository.AddAsync, commits. |
The behavior only audits commands — query requests reach the same generic interface but are filtered by the is ICommandBase check, so registering both behaviors application-wide is safe.
Quick start
// At composition time, alongside the other framework pipeline behaviors:
builder.Services.AddCommandAuditing();
That one call registers both behavior arities. The behavior types themselves are internal — they
are an implementation detail, not something to name from your composition root.
The behaviors resolve IWriteUnitOfWork from DI (ships with Stratara.EventSourcing.EntityFrameworkCore in the default deployment). No additional registration is needed.
Dependencies
Stratara.Abstractions— forIPipelineBehavior<,>,IRequest/IRequest<T>,ICommandBase,IWriteUnitOfWork,ICommandAuditRepository.JetBrains.Annotations—[UsedImplicitly]on the public behavior classes (DI-instantiated, no static call site).
At runtime an IWriteUnitOfWork implementation must be registered — typically by referencing Stratara.EventSourcing.EntityFrameworkCore and calling AddWriteStore(IConfiguration).
Security note — command payload contents
The audit row stores CommandTypeName and the serialized CommandJson of the dispatched command. Whatever fields your commands carry land in the audit table. Sensitive data (passwords, tokens, API keys, encryption material) MUST NOT live on a command record — or must be marked with [EncryptData] so the registered ISecureJsonSerializer encrypts them before persistence.
The default Stratara registration uses ISecureJsonSerializer (AES-GCM + tenant-scoped AAD) for the audit serialization, so [EncryptData]-annotated properties are protected. Plain-text properties go to disk unencrypted — treat the audit table accordingly when designing command shapes.
| 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
- JetBrains.Annotations (>= 2026.2.0)
- Stratara.Abstractions (>= 4.7.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.8.0 | 147 | 11/6/2026 |
| 4.7.1 | 130 | 11/5/2026 |
| 4.7.0 | 429 | 10/30/2026 |
| 4.6.1 | 112 | 10/29/2026 |
| 4.6.0 | 171 | 10/28/2026 |
| 4.5.0 | 261 | 10/28/2026 |
| 4.4.10 | 200 | 10/26/2026 |
| 4.4.9 | 105 | 10/26/2026 |
| 4.4.8 | 244 | 10/24/2026 |
| 4.4.7 | 118 | 10/23/2026 |
| 4.4.6 | 213 | 10/22/2026 |
| 4.4.5 | 283 | 10/14/2026 |
| 4.4.4 | 295 | 10/10/2026 |
| 4.4.3 | 138 | 10/10/2026 |
| 4.4.2 | 388 | 10/2/2026 |
| 4.4.1 | 361 | 9/29/2026 |
| 4.4.0 | 138 | 9/27/2026 |
| 4.3.1 | 141 | 9/25/2026 |
| 4.3.0 | 299 | 9/23/2026 |
| 4.2.0 | 144 | 9/18/2026 |
A release for one person who belongs to several tenants — and, sharing one identity store, to several applications.
### Added
- **`MembershipStatus.Former`** records a member who has left. It confers nothing — no role, permission or
cross-tenant access, never the tenant at sign-in, never a selection — and stays listed until the user's or the
tenant's erasure removes it.
- **`AddCheckedMembershipTenantClaim<TUser>()`**, a third tenant-claim mode: the claim is stamped at sign-in, kept when
the security-stamp validator refreshes a cookie sign-in, and checked on every request. A request whose user is no
longer an active member of the carried tenant loses the claim and resolves to the reserved default tenant, without
another tenant substituted. Only principals ASP.NET Identity issued are checked; an API key or a token the host
mints keeps its tenant. The tenant changes only when the host re-issues the sign-in. Combining it with
`AddMembershipTenantClaimsTransformation()` throws, and a claims transformation of the host's own registered
beside it is refused at start. Use it where several applications share one identity store:
`active_tenant` holds one selection per account, so live resolution moves every open session when any of them
switches.
- **`EventSubject.ForUser(userId)`** and **`EventSubject.NamesAnOwner`**: a stream can be created for a user alone,
for data that belongs to a person rather than to any of their tenants. It is recorded under the reserved default
tenant, keeps that owner for every later event whatever tenant the session names, and its encrypted fields — at
every level — are keyed to the person: shredded by the person's erasure, untouched by any tenant's.
`KeySubject.User` covers those keys too, so nothing is encrypted for the person again after the erasure.
- **`StrataraIdentityStore`, an identity store several hosts can share on PostgreSQL**, with its migrations shipped
in `Stratara.EventSourcing.EntityFrameworkCore`. It holds ASP.NET Identity's tables, passkeys included, and the
tenant directory in the fixed schema `stratara_identity`, with the history in
`stratara_identity.__stratara_identity_migrations`. `AddStrataraIdentityStore()` registers it on the connection
string `identitydb` (falling back to `defaultdb`, never through a tenant-routing `IDbResolver`) with the
directory's stores over it, and refuses a host that turns on `Stores.ProtectPersonalData`;
`MigrateStrataraIdentityStoreAsync()` creates the database where needed and applies the migrations — hosts that
migrate at once take turns. The account type is `IdentityUser` and cannot be extended, and the store fixes the
ASP.NET Identity schema version and key lengths, so every host's model matches the shipped migrations. Within a
major version the schema changes only additively. Moving an existing identity store onto it means replacing it and
seeding with the same user and tenant ids; the new guide *Shared Identity Store* describes it.
### Changed
- **Setting a membership to a status other than `Active` clears a selection that pointed at it**, as removing it
already did.
- **An explicit subject that names a user and no tenant is accepted** by `AppendOnBehalfOfAsync` and
`CreateOnBehalfOfAsync`; one that names neither is refused as before. A session whose tenant resolved to the
reserved default still gives an event no owner.
- **BREAKING (behaviour): an event or aggregate type marked `[EncryptData]` as a whole stops the host from starting.**
`EncryptionMetadataDriftGuard` refuses every registered aggregate, and every event type a registered aggregate
applies, that carries the attribute on the type; an event type no aggregate applies is refused when it is appended,
before anything is written. Once its subject was erased such a payload had nothing left to deliver, and a replay or
rebuild stopped there for good. Mark the properties instead; payloads already written as a whole are still read.
Commands and other types may still be marked as a whole.
### Fixed
- **A user's erasure shreds their own data through a key store that cannot list its scopes.** The eraser names the
user's keys under the reserved default tenant itself, at every level; until now only a listing reached the
user-level one.