Stratara.Identity.AspNetCore 4.1.1

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet add package Stratara.Identity.AspNetCore --version 4.1.1
                    
NuGet\Install-Package Stratara.Identity.AspNetCore -Version 4.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.Identity.AspNetCore" Version="4.1.1" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Stratara.Identity.AspNetCore" Version="4.1.1" />
                    
Directory.Packages.props
<PackageReference Include="Stratara.Identity.AspNetCore" />
                    
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.Identity.AspNetCore --version 4.1.1
                    
#r "nuget: Stratara.Identity.AspNetCore, 4.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.Identity.AspNetCore@4.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.Identity.AspNetCore&version=4.1.1
                    
Install as a Cake Addin
#tool nuget:?package=Stratara.Identity.AspNetCore&version=4.1.1
                    
Install as a Cake Tool

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. ApplyStrataraLockoutDefaults runs inside AddAspNetIdentityWithSignInManager only — the bare AddAspNetIdentity leaves ASP.NET Identity's own lockout defaults in place. If you wire sign-in yourself on top of AddAspNetIdentity, configure IdentityOptions.Lockout explicitly; otherwise password attempts are not throttled the way the rest of this package assumes. | 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. | | DependencyInjection/MembershipClaimsServiceCollectionExtensions + Services/MembershipClaims* | Sign-in tenant-claim bridge: AddMembershipTenantClaim<TUser>() (stamp stratara:tenant_id at issuance) and AddMembershipTenantClaimsTransformation() (resolve live per request) | | Authorization/* + DependencyInjection/PermissionPolicyServiceCollectionExtensions | AddStrataraPermissionPolicies() — every catalog permission becomes an on-demand [Authorize("...")] policy backed by IPermissionResolver | | Authentication/ApiKey* + DependencyInjection/ApiKeyAuthenticationExtensions | AddStrataraApiKey() (X-Api-Key scheme over IApiKeyStore) and AddStrataraAuthSchemeSelector() (route API-key vs. Bearer vs. cookie by request shape) | | Authentication/Stratara{OpenIdConnect,JwtBearer}Options + DependencyInjection/OpenIdConnectAuthenticationExtensions | AddStrataraOpenIdConnect(configuration) (interactive external login) and AddStrataraJwtBearer(configuration) (API access-token validation, multi-issuer by iss) | | 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 for SignInManager, 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 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

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.2.0 48 9/18/2026
4.1.1 75 9/16/2026
4.1.0 77 9/16/2026
4.0.4 680 9/14/2026
4.0.3 115 9/3/2026
4.0.2 593 9/3/2026
4.0.1 227 9/2/2026
4.0.0 643 8/31/2026
4.0.0-preview.1 62 8/31/2026
3.4.0 137 8/28/2026
3.3.0 332 8/25/2026
3.2.3 104 8/22/2026
3.2.2 725 8/14/2026
3.2.1 704 8/2/2026
3.2.0 116 7/18/2026
3.1.7 131 7/1/2026
3.1.6 536 6/22/2026
3.1.5 122 6/22/2026
3.1.4 128 6/15/2026
3.1.3 126 6/10/2026
Loading failed

Correctness fixes for the Orleans execution model ahead of production use. Recorded commands can no longer
reach a bus drain, a durable timer fires once however long its handler runs, and heavy commands are
specified as the exception to the one-writer-per-aggregate promise they always were. The execution-model
reset removes only the host's own checkpoints, and three store-level fixes land for the partition
counter, its backfill and a checkpoint's first write. No schema change; **stop every bus outbox worker
before upgrading hosts that record commands through the execution model**, and register
`AddStrataraIntentStore` on the silos that run the drain.

### Changed

- **Orleans: the execution-model reset removes only the checkpoints of the host's own projections and
 sagas.** It removed every checkpoint in the read store, so a reset in one deployment made another
 deployment sharing the read store rebuild its projections unasked. The reset now removes the
 checkpoints of the projections and sagas registered in the composition it is resolved from, and the
 report counts only those. A checkpoint of a projection the host no longer registers stays; nothing
 reads it. Resolve the reset from the host's own composition — one that registers no store reader
 removes no checkpoint.
- **The documentation states when a read store can be shared.** Checkpoints are keyed by consumer, not
 by deployment: deployments sharing a read store need distinct projection names, and at most one of
 them runs `AddStrataraSagaGrains`.
- **Orleans: heavy commands are specified as running outside their aggregate's turn and order.** They
 always ran in their own bounded pool beside the aggregate's other commands; the specification promised
 otherwise. Their hand-over no longer holds the per-aggregate send order either: a command dispatched after
 a heavy command for the same aggregate no longer waits for it, and two due heavy commands on one aggregate
 no longer hold up the drain's resume pass. Where a heavy command and another command on the same aggregate
 both append, the store's version check refuses the later one, which is resumed like any failing command.
- **Orleans: a recorded command is stored under a kind of its own.** No bus outbox drain reads it any more.
 Commands recorded under 4.1.0 are still resumed; stop every bus outbox worker before upgrading hosts that
 record commands.

### Fixed

- **Orleans: the outbox drain no longer publishes recorded commands to the bus.** It chose between resuming
 recorded commands and publishing stored commands by whether the execution model's dispatcher was
 registered on its own silo, and the migration guide registers the dispatcher on the API host and the drain
 on the silos. Such a silo handed every recorded command — kept ones included — to the bus: commands ran
 twice, kept commands came back, the attempt bound did not hold. The drain now resumes recorded commands
 wherever an intent store is registered and warns (`117_111`) where recorded commands exist but none is.
 Register `AddStrataraIntentStore` on the silos that run the drain.
- **Orleans: a durable timer fires once however long its handler runs.** A handler that outlasted the
 reminder call's response timeout was started again by the next tick. A tick that arrives while the same
 timer's handler runs now does nothing, and a tick confirms its timer is still registered before firing.

- **Orleans: two writers of the same first checkpoint no longer fail one of them.** When an
 activation and its successor overlap during a failover, both can find no checkpoint row and both
 insert it; the one that lost to the key threw. It now updates the row the other inserted.
- **Orleans: the partition counter works on a model that does not use snake-case names.** The
 interceptor advanced the counter with SQL naming `partition_position` and its columns literally, so
 a write context mapping the counter under other names failed every append. It now goes through the
 context's model, as the native reader already did.
- **Orleans: the partition-counter backfill positions old entries in the order they were appended.**
 It ordered each partition's history by bucket first, so a projection or saga reading across
 aggregates saw the facts of one bucket before earlier facts of another. Entries are now positioned
 in sequence order, as the event-sourcing-store specification already promised. A store backfilled
 under 4.1.0 keeps the positions it was given; the backfill does not reposition entries.