Stratara.Identity.AspNetCore
4.4.1
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Identity.AspNetCore --version 4.4.1
NuGet\Install-Package Stratara.Identity.AspNetCore -Version 4.4.1
<PackageReference Include="Stratara.Identity.AspNetCore" Version="4.4.1" />
<PackageVersion Include="Stratara.Identity.AspNetCore" Version="4.4.1" />
<PackageReference Include="Stratara.Identity.AspNetCore" />
paket add Stratara.Identity.AspNetCore --version 4.4.1
#r "nuget: Stratara.Identity.AspNetCore, 4.4.1"
#:package Stratara.Identity.AspNetCore@4.4.1
#addin nuget:?package=Stratara.Identity.AspNetCore&version=4.4.1
#tool nuget:?package=Stratara.Identity.AspNetCore&version=4.4.1
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.1)
- Stratara.Shared (>= 4.4.1)
- 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 | 34 | 10/2/2026 |
| 4.4.1 | 350 | 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 | 920 | 9/14/2026 |
| 4.0.3 | 120 | 9/3/2026 |
| 4.0.2 | 598 | 9/3/2026 |
| 4.0.1 | 276 | 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 | 107 | 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 errors that were not errors. Where two writers insert the same row at once — two
deliveries forgetting a deleted tenant, two activations writing a partition's first checkpoint, two
hosts importing one API key — the framework already recovered, but EF Core had logged the losing
statement at Error first; on PostgreSQL and SQLite the insert now skips a row that is already there.
And a RabbitMQ bus whose broker went away first no longer reports a warning for every subscription it
stops, nor a failed handler for a message it merely could not acknowledge. No migration and no
configuration change is needed.
### Fixed
- **Forgetting a deleted tenant leaves no error in the log when two deliveries race.** A tenant's two
deletion facts arrive in two bundles, so two deliveries of one projection can record the same tenant
at once. The losing insert was caught and the tenant recorded all the same, but EF Core had already
logged the failed statement at Error (`20102` and `10000`), so a customer deletion could leave two
errors in a projection worker's log. On PostgreSQL and SQLite the tenants are now recorded with an
insert that skips a row already there; on other providers the store still retries, and EF Core still
logs the statement that lost.
- **A projection checkpoint's first write, and an API key two hosts import at once, leave no error in
the log.** Two activations of one reader that overlap during a failover can both write a partition's
first checkpoint, and hosts that seed the same key as they boot import it at once. The writer whose
insert lost recovered — it took the other's checkpoint over, or adopted the other's key — but EF Core
had already logged the failed statement at Error. On PostgreSQL and SQLite the insert now skips a row
that is already there, as the record of forgotten tenants does; a checkpoint that another writer
inserted and removed again before it could be taken over is refused with an
`InvalidOperationException`. An import takes that path only where it is the only write on its
context, and then writes the key and its membership in one transaction of its own, outside
`SaveChanges` and its interceptors. An import on a context with unsaved changes or inside a
transaction of the caller's saves through `SaveChanges` as before, and so does a table a consumer
widened with columns the row does not carry, and every other provider: there the writer still
recovers, and EF Core still logs the statement that lost.
- **A RabbitMQ subscription whose broker is already gone stops without a warning.** When a stack stops
its broker before its hosts, a stopping subscription's cancel met a connection that had already
closed, or that closed while the cancel waited for its reply, and every subscription of every host
logged `108_107` at Warning — new in 4.4.0, which made a subscription cancel its consumer before it
closes. A closed connection has no consumer left to cancel, which is where the stop was going, so
this is now logged at Debug as `108_007` (`LogEvents.Messaging.SubscriptionAlreadyClosed`). A cancel
that fails while the connection is still up still warns.
- **A handler that completes after the broker went away is no longer reported as failed.** Its
acknowledgement met a closed channel, and the RabbitMQ bus logged `108_101` at Error although the
handler had succeeded, then tried to reject the message on the same closed channel. It now logs
`108_008` (`LogEvents.Messaging.MessageNotSettledChannelClosed`) at Information: the message could
not be settled, and the broker delivers it again.