Stratara.Identity.AspNetCore
4.4.2
Prefix Reserved
dotnet add package Stratara.Identity.AspNetCore --version 4.4.2
NuGet\Install-Package Stratara.Identity.AspNetCore -Version 4.4.2
<PackageReference Include="Stratara.Identity.AspNetCore" Version="4.4.2" />
<PackageVersion Include="Stratara.Identity.AspNetCore" Version="4.4.2" />
<PackageReference Include="Stratara.Identity.AspNetCore" />
paket add Stratara.Identity.AspNetCore --version 4.4.2
#r "nuget: Stratara.Identity.AspNetCore, 4.4.2"
#:package Stratara.Identity.AspNetCore@4.4.2
#addin nuget:?package=Stratara.Identity.AspNetCore&version=4.4.2
#tool nuget:?package=Stratara.Identity.AspNetCore&version=4.4.2
Stratara.Identity.AspNetCore
Derived. The behaviour described here is specified under
openspec/specs/. Those specifications are the source; this page explains and illustrates them.
License: MIT.
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/AspCoreIdentityHostBuilderExtensions |
AddAspNetIdentity<TUser, TIdentityDbContext>() (Stratara password/schema-v3/passkey defaults — no lockout), AddAspNetIdentityWithSignInManager<TUser, TIdentityDbContext>() (same + lockout defaults + AspNetSignInManager + localization), AddDevelopmentNoOpEmailSender<TUser>() (dev-only, throws in Production) |
Lockout only ships with the sign-in manager.
ApplyStrataraLockoutDefaultsruns insideAddAspNetIdentityWithSignInManageronly — the bareAddAspNetIdentityleaves ASP.NET Identity's own lockout defaults in place. If you wire sign-in yourself on top ofAddAspNetIdentity, configureIdentityOptions.Lockoutexplicitly; otherwise password attempts are not throttled the way the rest of this package assumes. |Services/AspNetSignInManager<TUser>| WrapsSignInManager<TUser>+UserManager<TUser>and producesStrataraSignInResultwith 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 inIdentityResources.resx;IdentityResources.de.resxprovides German overrides.AddAspNetIdentityWithSignInManagercallsAddLocalization()soIStringLocalizer<IdentityResources>resolves automatically. | |DependencyInjection/MembershipClaimsServiceCollectionExtensions+Services/MembershipClaims*| Sign-in tenant-claim bridge:AddMembershipTenantClaim<TUser>()(stampstratara:tenant_idat issuance) andAddMembershipTenantClaimsTransformation()(resolve live per request) | |Authorization/*+DependencyInjection/PermissionPolicyServiceCollectionExtensions|AddStrataraPermissionPolicies()— every catalog permission becomes an on-demand[Authorize("...")]policy backed byIPermissionResolver| |Authentication/ApiKey*+DependencyInjection/ApiKeyAuthenticationExtensions|AddStrataraApiKey()(X-Api-Key scheme overIApiKeyStore) andAddStrataraAuthSchemeSelector()(route API-key vs. Bearer vs. cookie by request shape) | |Authentication/Stratara{OpenIdConnect,JwtBearer}Options+DependencyInjection/OpenIdConnectAuthenticationExtensions|AddStrataraOpenIdConnect(configuration)(interactive external login) andAddStrataraJwtBearer(configuration)(API access-token validation, multi-issuer byiss) | |Services/ExternalLoginProvisioningService<TUser>+DependencyInjection/ExternalLoginProvisioningExtensions|AddStrataraExternalLoginProvisioning<TUser>()— hardened JIT create/link of local accounts on first external sign-in (see below) |
Localization
AspNetSignInManager resolves its four user-facing failure messages (Identity.SignIn.Lockout, Identity.SignIn.InvalidCredentials, Identity.SignIn.InvalidTwoFactor, Identity.SignIn.InvalidRecoveryCode) via IStringLocalizer<IdentityResources>. A "not allowed" sign-in deliberately maps onto the InvalidCredentials message rather than getting its own, to avoid confirming that an account exists. 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.
External login (OpenID Connect) + JIT provisioning
Add external identity providers as ordinary authentication schemes and provision local accounts on first sign-in:
builder.Services
.AddAuthentication(StrataraAuthSchemeSelectorOptions.SchemeName)
.AddCookie(IdentityConstants.ApplicationScheme)
.AddStrataraOpenIdConnect(builder.Configuration) // interactive "log in with <provider>"
.AddStrataraJwtBearer(builder.Configuration) // API access-token validation (iss-routed)
.AddStrataraAuthSchemeSelector(); // route Bearer vs. cookie per request
builder.Services.AddStrataraExternalLoginProvisioning<ApplicationUser>();
AddStrataraOpenIdConnect binds Identity:OpenIdConnect (Authority, ClientId, ClientSecret,
Scopes) and AddStrataraJwtBearer binds Identity:JwtBearer (Authority, Audience, ValidIssuers).
Both key the principal on the issuer sub, never on email — Entra, Keycloak, and generic OIDC differ
only in configuration.
ExternalLoginProvisioningService<TUser> creates or links the local account on a first external
sign-in with the account-takeover defenses on by default: it links on the issuer's (provider, sub);
auto-links to a pre-existing account only when the email is verified by the provider
(email_verified/xms_edov) and already confirmed locally — otherwise it returns
RequiresInteractiveLinking and refuses to merge; honors an optional invitation gate and an
AutoProvision switch; and fails closed. Call it from your sign-in callback (for example the OpenID
Connect OnTicketReceived event). The Stratara.Sample.Identity sample shows the full wiring.
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.AspNetCore.Authentication.OpenIdConnect,Microsoft.AspNetCore.Authentication.JwtBearer— external-login OIDC + API bearer-token schemes.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.Authentication.JwtBearer (>= 10.0.11)
- Microsoft.AspNetCore.Authentication.OpenIdConnect (>= 10.0.11)
- Microsoft.AspNetCore.Identity.EntityFrameworkCore (>= 10.0.11)
- Microsoft.IdentityModel.JsonWebTokens (>= 8.22.0)
- Stratara.Identity.Core (>= 4.4.2)
- Stratara.Shared (>= 4.4.2)
- System.IdentityModel.Tokens.Jwt (>= 8.22.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.4.2 | 43 | 10/2/2026 |
| 4.4.1 | 364 | 9/29/2026 |
| 4.4.0 | 125 | 9/27/2026 |
| 4.3.1 | 111 | 9/25/2026 |
| 4.3.0 | 387 | 9/23/2026 |
| 4.2.0 | 142 | 9/18/2026 |
| 4.1.1 | 96 | 9/16/2026 |
| 4.1.0 | 95 | 9/16/2026 |
| 4.0.4 | 921 | 9/14/2026 |
| 4.0.3 | 120 | 9/3/2026 |
| 4.0.2 | 598 | 9/3/2026 |
| 4.0.1 | 282 | 9/2/2026 |
| 4.0.0 | 671 | 8/31/2026 |
| 4.0.0-preview.1 | 71 | 8/31/2026 |
| 3.4.0 | 142 | 8/28/2026 |
| 3.3.0 | 338 | 8/25/2026 |
| 3.2.3 | 108 | 8/22/2026 |
| 3.2.2 | 727 | 8/14/2026 |
| 3.2.1 | 715 | 8/2/2026 |
| 3.2.0 | 119 | 7/18/2026 |
A release about a flag that cost too much. Every host sharing the replay coordination state over Redis
asked Redis, with a blocking round trip on the calling thread, whether a replay was active — and the
Orleans execution model asked on every hot path, eight to ten times per command on a host with three
projections, inside grain turns. On a two-core host that was enough to starve the thread pool and time
the Redis connection out, surfacing as failed catch-ups, lagging read models and failed grain
registrations although no replay ever ran. The answer now comes from memory. No migration is needed;
one optional setting is new.
### Fixed
- **No path waits on Redis to learn whether a replay is active.** The Redis-backed replay state answers
`IsReplayActive` from a field. A change made in the host itself is seen there at once; a change made
elsewhere — a replay that began or ended in another host, or a marking that lapsed — is announced over
a channel beside the replay-request channel and seen within its latency, and every host re-reads the
marking every `ProjectionReplay:RefreshSeconds` regardless, as the safety net for a lost announcement.
The Orleans execution model's command dispatcher, bundle dispatcher, store readers and drain, and the
bus dispatchers, make no Redis call for it any more. Nothing changes for a host without Redis, whose
state was in process already, nor for a host that registers its own `IProjectionReplayState`.
### Added
- **`ProjectionReplayOptions.RefreshSeconds`** (default 5), read from the `ProjectionReplay` section
like the lease. It bounds how long a host answers from a replay marking that changed elsewhere where the
announcement was lost. Refused when the host starts at zero or below, and at or above
`LeaseSeconds`, with an `OptionsValidationException` naming `ProjectionReplay:RefreshSeconds`.
- **Log events `104_015` to `104_018`.** A host that cannot refresh the replay marking from Redis says
so once at Warning (`104_015`) and keeps its last answer; `104_016` at Information says it reads the
marking again. A host that cannot subscribe to the marking's announcements says so once at Warning
(`104_017`), sees a change on the refresh period only, and `104_018` says it is subscribed again.
### Changed
- **A host that cannot reach Redis keeps its last answer about the replay.** Before, every dispatch and
every catch-up on such a host failed with the connection's exception. Now they proceed on what the host
last learned — initially that no replay is active — and the loss is logged once. The replay stays
correct regardless: on the Orleans execution model the readers are paused by the rebuild and the
replay themselves, and apply the store from the beginning once more when the replay ends.
- **Rolling upgrade.** A host on a release before this one announces nothing when it starts or ends a
replay, so a host on this release sees that replay at the refresh period rather than at once. The
marking, its key and its lease are unchanged, so the two releases share one replay state.