Stratara.Identity.AspNetCore
3.1.5
See the version list below for details.
dotnet add package Stratara.Identity.AspNetCore --version 3.1.5
NuGet\Install-Package Stratara.Identity.AspNetCore -Version 3.1.5
<PackageReference Include="Stratara.Identity.AspNetCore" Version="3.1.5" />
<PackageVersion Include="Stratara.Identity.AspNetCore" Version="3.1.5" />
<PackageReference Include="Stratara.Identity.AspNetCore" />
paket add Stratara.Identity.AspNetCore --version 3.1.5
#r "nuget: Stratara.Identity.AspNetCore, 3.1.5"
#:package Stratara.Identity.AspNetCore@3.1.5
#addin nuget:?package=Stratara.Identity.AspNetCore&version=3.1.5
#tool nuget:?package=Stratara.Identity.AspNetCore&version=3.1.5
Stratara.Identity.AspNetCore
License: FSL-1.1-MIT (Functional Source License — source-available; converts to MIT after 2 years). Not OSI-approved OSS.
Channel-agnostic ASP.NET Core identity wiring for the Stratara stack. Provides the AddAspNetIdentity / AddAspNetIdentityWithSignInManager extension methods and an IStrataraSignInManager wrapper around the ASP.NET Core SignInManager. Channel-specific glue (Blazor Server's AuthenticationStateProvider, MAUI session-state forwarders, etc.) is the consumer's responsibility — Stratara intentionally stops at the ASP.NET-Core-generic surface to stay application-agnostic.
What's in the box
| Folder | Contents |
|---|---|
DependencyInjection/AspCoreIdentityServiceCollectionExtensions |
AddAspNetIdentity<TUser, TIdentityDbContext>() (Stratara password/lockout/schema-v3/passkey defaults), AddAspNetIdentityWithSignInManager<TUser, TIdentityDbContext>() (same + AspNetSignInManager + localization), AddDevelopmentNoOpEmailSender<TUser>() (dev-only, throws in Production) |
Services/AspNetSignInManager<TUser> |
Wraps SignInManager<TUser> + UserManager<TUser> and produces StrataraSignInResult with already-localized failure messages |
Services/IdentityNoOpEmailSender<TUser> |
Development-time email sender that drops every email (Task.CompletedTask); replace in production |
Resources/IdentityResources |
Resource-anchor for sign-in failure messages. English default ships in IdentityResources.resx; IdentityResources.de.resx provides German overrides. AddAspNetIdentityWithSignInManager calls AddLocalization() so IStringLocalizer<IdentityResources> resolves automatically. |
Localization
AspNetSignInManager resolves its five user-facing failure messages (Identity.SignIn.Lockout, NotAllowed, InvalidCredentials, InvalidTwoFactor, InvalidRecoveryCode) via IStringLocalizer<IdentityResources>. Languages out of the box: English (default) and German (de). To add another culture, ship a satellite .resx (e.g. IdentityResources.fr.resx) in your own assembly and register a chained IStringLocalizer<IdentityResources> if needed. Selection follows CultureInfo.CurrentUICulture — wire up app.UseRequestLocalization(...) to map this from the request.
Quick start
// Channel-agnostic ASP.NET Core host (MVC, Razor Pages, Minimal API, ...):
builder.AddAspNetIdentityWithSignInManager<ApplicationUser, IdentityDbContext>();
// Or for a host without sign-in manager (e.g. a worker that only needs identity stores):
builder.AddAspNetIdentity<ApplicationUser, IdentityDbContext>();
For Blazor Server hosts, additionally register your own IStrataraAuthenticationStateProvider implementation (and the AuthenticationStateProvider forwarder). Stratara does not ship a Blazor-specific provider — the previous BlazorAuthenticationStateProvider lived here in 1.x but moved out in v2.0.0 to keep this package application-agnostic.
Dependencies
Stratara.Identity.Core— channel-agnostic abstractions (IStrataraSignInManager,IStrataraAuthenticationStateProvider) + shared model records.Stratara.Shared— multitenancy + session-context types.Microsoft.AspNetCore.App— shared framework reference forSignInManager,IEmailSender<TUser>, etc.Microsoft.AspNetCore.Identity.EntityFrameworkCore— ASP.NET Identity stores.Microsoft.IdentityModel.JsonWebTokens,System.IdentityModel.Tokens.Jwt— JWT helpers for token-based flows.
| 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
- Microsoft.AspNetCore.Identity.EntityFrameworkCore (>= 10.0.8)
- Microsoft.IdentityModel.JsonWebTokens (>= 8.18.0)
- Stratara.Identity.Core (>= 3.1.5)
- Stratara.Shared (>= 3.1.5)
- System.IdentityModel.Tokens.Jwt (>= 8.18.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
### Added
- **Configurable snapshot strategy** (`Stratara.Abstractions`, `Stratara.Infrastructure`) — the
snapshot cadence is no longer hard-coded. A new `Stratara.Abstractions.EventSourcing.ISnapshotStrategy`
decides, per stream, whether the event-sourcing runtime should write a snapshot:
`bool ShouldSnapshot(Type aggregateType, long currentVersion, long lastSnapshotVersion)`.
`AddEventSourcing()` registers the default `VersionThresholdSnapshotStrategy` (snapshot every 50
versions — identical to the previous behaviour) via `TryAddSingleton`, so existing consumers see no
change. To take over the policy, register your own singleton `ISnapshotStrategy` (it overrides the
default whether registered before or after `AddEventSourcing()`): vary the threshold per aggregate
type, construct `new VersionThresholdSnapshotStrategy(threshold)` for a different uniform cadence, or
register `NoSnapshotStrategy` to disable snapshotting entirely. This replaces the previously
hard-coded `UseSnapshots`/`SnapshotRange` constants in the default snapshot service, which were not
actually configurable despite the documentation implying they were.
- **`AddDomainEventTypesFromAssemblyContaining<T>()`** (`Stratara.Abstractions`) — registers *only* the
domain event types consumed by an assembly's aggregate `Apply(TEvent)` methods in the trusted-type
resolver, without registering the aggregate types themselves and without pulling any projection / saga
/ command-handler classes into DI. Use it in a host that only needs to deserialize event payloads off
the message bus or event stream — typically a dedicated projection or saga worker — but must not wire
the handler classes (and their runtime dependencies) that `AddProjectionsFromAssemblyContaining<T>`
would register. Complements the existing `AddAggregatesFromAssemblyContaining<T>` (which additionally
registers the aggregate types) and `AddTrustedType<T>` (single type).