NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet
NuGet, #1984 most downloaded on NuGet
EntityFramework persistence layer for Duende IdentityServer
Latest stable
8.0.11
Last release 6 days ago
16 Nov 2026
Release timing varies
gaps range from 8 days to 3 months
Some releases are documented
notes for 24 of 51 stable releases
51 versions withdrawn
withdrawn after publishing
127 years old
102 releases · first in 1900
Drag across the ruler to compare, or tap a release to open it.
If you replaced IServerSideTicketStore with your own implementation, upgrading doesn't fix the vulnerability for you; see the advisory for the change…
We've published several security advisories for Duende products including IdentityServer and BFF, along with updated packages that fix them. We strongly recommend updating to the latest patched releases.
The fixes that aren't SAML-specific are also released in 7.4.15, 7.3.6, 7.2.6, 7.1.4 and 7.0.11.
mTLS: if you call AddMutualTlsSecretValidators(), make sure the certificate authentication scheme (MutualTls.ClientCertificateAuthenticationScheme, Certificate by default) is registered, usually with AddCertificate(). Clients with a thumbprint (X509Thumbprint) secret that present a self-signed certificate keep working only if AllowedCertificateTypes includes CertificateTypes.SelfSigned. Clients that use a self-signed certificate with a subject name (X509Name) secret must switch to a thumbprint secret or a CA-issued certificate.
Introspection: public clients and implicit-only clients can no longer call the introspection endpoint; it returns 401 for them. Give applications that relied on this a confidential client.
End session: an id_token_hint that isn't an ID token, or that has no sub claim, is ignored, and the user sees the sign-out prompt. If your ID tokens have a custom typ header, add it to IdentityServerOptions.IdentityTokenJwtTypes.
Server-side sessions: a user who signs in on a browser that still carries another user's session is signed out, and has to sign in a second time. If you replaced IServerSideTicketStore with your own implementation, upgrading doesn't fix the vulnerability for you; see the advisory for the change to make.
DPoP: if you override DefaultDPoPProofValidator.ValidateSignatureAsync, replaced the Handler of JwtRequestValidator, or registered your own secret validator for client assertions, see the advisory for what your code must check.
SAML XML limits: SAML messages whose XML elements are nested deeper than MaxXmlNestingDepth (32 by default) are rejected. You can change the limit for the identity provider (SamlOptions.MaxXmlNestingDepth), for service providers configured in code (SamlServiceProviderOptions.MaxXmlNestingDepth) and for SAML dynamic providers. The service provider now also rejects messages that contain a DTD and drops XML processing instructions, as the identity provider already did.
SAML logout with an external login callback: if you use SAML dynamic providers (AddSamlDynamicProvider()), or AddSamlServiceProvider() with the external cookie as its sign-in scheme, your external login callback creates the IdentityServer session. Copy the SAML sign-in claims into that session, or IdP-initiated logout stays exposed after the upgrade. In our templates, add this to CaptureExternalLoginContext in Pages/ExternalLogin/Callback.cshtml.cs, right after the block that copies the sid claim:
localClaims.AddRange(externalResult.Principal.Claims.Where(claim => claim.Type
is "https://duendesoftware.com/Saml2/Scheme"
or "https://duendesoftware.com/Saml2/LogoutNameIdentifier"
or "https://duendesoftware.com/Saml2/SessionIndex"));SAML logout and SameSite: if your session cookie uses SameSite=Lax or SameSite=Strict and an identity provider sends its LogoutRequest with the HTTP-POST binding, the logout no longer ends the IdentityServer session. The default, SameSite=None, isn't affected.
WebApplicationFactory, no longer hangs.Full Changelog: is-8.0.10...is-8.0.11
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Most of the October 2026 .NET vulnerabilities are in the ASP.NET Core shared framework, so upgrading IdentityServer doesn't fix them. Update every Ide…
This release moves IdentityServer's dependencies onto the .NET October 2026 security updates, and fixes an exception during access token validation.
Most of the October 2026 .NET vulnerabilities are in the ASP.NET Core shared framework, so upgrading IdentityServer doesn't fix them. Update every IdentityServer host and container image to the October 2026 .NET runtime. For IdentityServer, the most important fixes are:
System.Security.Cryptography.Xml loads from the shared framework, so these fixes come from the runtime, not from this package.See Microsoft's .NET security announcements for the full list.
Microsoft.IdentityModel dependencies are raised to the October 2026 patched releases.sub claim but no resolvable client is now rejected with invalid_token, instead of throwing a NullReferenceException during user activity validation. Tokens without a sub claim, including custom JWTs issued without a client, are unaffected.None.
Full Changelog: is-8.0.9...is-8.0.10
This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 8.0.x users upgrad
This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 8.0.x users upgrade.
client_id does not exactly match the authenticated client, as required by RFC 9126. Custom IPushedAuthorizationRequestValidator implementations remain responsible for enforcing this binding.AllowUnregisteredPushedRedirectUris. These clients do not authenticate at the PAR endpoint, so they must register their redirect URIs.AllowUnregisteredPushedRedirectUris is enabled, unregistered redirect URIs must now use the https scheme and must not match ValidationOptions.InvalidRedirectUriPrefixes. Registered redirect URIs, loopback handling, and custom redirect URI validators are unchanged.https PAR redirect URIs (for example http://localhost during local development) must be registered or moved to https.Full Changelog: is-8.0.8...is-8.0.9
Duende IdentityServer 8.0.9 Latest
Latest
Compare
A patch release containing some SAML bug fixes and improvements. Also, based on customer feedback regarding logging in Identity Server, we have reduc
A patch release containing some SAML bug fixes and improvements. Also, based on customer feedback regarding logging in Identity Server, we have reduced the severity of select log messages.
Note: We are currently auditing all Identity Server log levels and will roll out further adjustments in upcoming releases.
SAML: Adds configurable outbound AuthnRequest signing when IdentityServer acts as a SAML service provider. Both static and dynamic provider configurations can select Never or Always, with safe defaults, certificate-presence validation, consistent metadata, and persisted dynamic-provider behavior.
SAML logout sessions currently use the protected logout-message handle as their database lookup key. That protected value grows with serialized logout state and can exceed the nvarchar(200) column, causing SAML logout to fail with a truncation error.
Fixed issue when calling both AddInMemoryClients and AddInMemorySamlProviders that the last call overwrites the first call.
This is a patch release of IdentityServer that fixes the following issue:
This is a patch release of IdentityServer that fixes the following issue:
This is a patch release of IdentityServer that fixes the following issue:
This is a patch release of IdentityServer that fixes the following issue:
DiagnosticHostedService failed when certain delegate-based options were configured (e.g., dynamic provider path matching)This is a patch release of IdentityServer that fixes the following issue:
This is a patch release of IdentityServer that fixes the following issue:
This is a patch release of IdentityServer that adds support for IDP-initiated SSO when IdentityServer acts as a SAML Service Provider.
This is a patch release of IdentityServer that adds support for IDP-initiated SSO when IdentityServer acts as a SAML Service Provider.
AddSamlServiceProvider() or dynamic SAML providers), it can now receive unsolicited authentication responses from upstream identity providers. Configure AllowUnsolicitedAuthnResponse = true and set IdpInitiatedCallbackUrl to your external login callback endpoint.AuthenticationProperties.Items["relayState"], allowing your callback to use it for routing, tenant resolution, or other application logic.MaxRelayStateLength (default 1024 bytes) controls the maximum size of RelayState that will be persisted in authentication properties, preventing cookie bloat from oversized values.https://duendesoftware.com/Saml2. Users with active SAML SP sessions at the time of upgrade may experience failed single logout correlation until they re-authenticate. This only affects deployments using the SAML Service Provider feature (AddSamlServiceProvider() or dynamic SAML providers).Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
If you replaced IServerSideTicketStore with your own implementation, upgrading doesn't fix the vulnerability for you; see the advisory for the change…
We've published several security advisories for Duende products including IdentityServer and BFF, along with updated packages that fix them. We strongly recommend updating to the latest patched releases.
The same fixes are released in 8.0.11, 7.4.15, 7.3.6, 7.2.6, 7.1.4 and 7.0.11.
AddMutualTlsSecretValidators(), make sure the certificate authentication scheme (MutualTls.ClientCertificateAuthenticationScheme, Certificate by default) is registered, usually with AddCertificate(). Clients with a thumbprint (X509Thumbprint) secret that present a self-signed certificate keep working only if AllowedCertificateTypes includes CertificateTypes.SelfSigned. Clients that use a self-signed certificate with a subject name (X509Name) secret must switch to a thumbprint secret or a CA-issued certificate.id_token_hint that isn't an ID token, or that has no sub claim, is ignored, and the user sees the sign-out prompt. If your ID tokens have a custom typ header, add it to IdentityServerOptions.IdentityTokenJwtTypes.IServerSideTicketStore with your own implementation, upgrading doesn't fix the vulnerability for you; see the advisory for the change to make.DefaultDPoPProofValidator.ValidateSignatureAsync, replaced the Handler of JwtRequestValidator, or registered your own secret validator for client assertions, see the advisory for what your code must check.WebApplicationFactory, no longer hangs.Full Changelog: is-7.4.14...is-7.4.15
Most of the October 2026 .NET vulnerabilities are in the ASP.NET Core shared framework, so upgrading IdentityServer doesn't fix them. Update every Ide…
This release moves IdentityServer's dependencies onto the .NET October 2026 security updates, and fixes an exception during access token validation.
Most of the October 2026 .NET vulnerabilities are in the ASP.NET Core shared framework, so upgrading IdentityServer doesn't fix them. Update every IdentityServer host and container image to the October 2026 .NET runtime for the .NET version you run. For IdentityServer, the most important fixes are:
See Microsoft's .NET security announcements for the full list.
sub claim but no resolvable client is now rejected with invalid_token, instead of throwing during user activity validation. Tokens with neither sub nor client_id, and valid tokens with a client, are validated as before.None.
Full Changelog: is-7.4.13...is-7.4.14
This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 7.4.x users upgrad
This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 7.4.x users upgrade.
client_id does not exactly match the authenticated client, as required by RFC 9126. Custom IPushedAuthorizationRequestValidator implementations remain responsible for enforcing this binding.AllowUnregisteredPushedRedirectUris. These clients do not authenticate at the PAR endpoint, so they must register their redirect URIs.AllowUnregisteredPushedRedirectUris is enabled, unregistered redirect URIs must now use the https scheme and must not match ValidationOptions.InvalidRedirectUriPrefixes. Registered redirect URIs, loopback handling, and custom redirect URI validators are unchanged.https PAR redirect URIs (for example http://localhost during local development) must be registered or moved to https.Full Changelog: is-7.4.12...is-7.4.13
Based on customer feedback regarding logging in Identity Server, we have reduced the severity of select log messages:
Based on customer feedback regarding logging in Identity Server, we have reduced the severity of select log messages:
Note: We are currently auditing all Identity Server log levels and will roll out further adjustments in upcoming releases.
This is a patch release of IdentityServer that fixes the following issue:
This is a patch release of IdentityServer that fixes the following issue:
DiagnosticHostedService failed when certain delegate-based options were configured (e.g., dynamic provider path matching)This is a patch release of IdentityServer that fixes the following issue:
This is a patch release of IdentityServer that fixes the following issue:
This is a patch release of identity server that fixes the following issue:
This is a patch release of identity server that fixes the following issue:
Microsoft.Bcl.Memory dependency for net8.0 to resolve .NET 8 runtime failures at discovery and related endpoints.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
If you replaced IServerSideTicketStore with your own implementation, upgrading doesn't fix the vulnerability for you; see the advisory for the change…
We've published several security advisories for Duende products including IdentityServer and BFF, along with updated packages that fix them. We strongly recommend updating to the latest patched releases.
The same fixes are released in 8.0.11, 7.4.15, 7.3.6, 7.2.6, 7.1.4 and 7.0.11.
AddMutualTlsSecretValidators(), make sure the certificate authentication scheme (MutualTls.ClientCertificateAuthenticationScheme, Certificate by default) is registered, usually with AddCertificate(). Clients with a thumbprint (X509Thumbprint) secret that present a self-signed certificate keep working only if AllowedCertificateTypes includes CertificateTypes.SelfSigned. Clients that use a self-signed certificate with a subject name (X509Name) secret must switch to a thumbprint secret or a CA-issued certificate.id_token_hint that isn't an ID token, or that has no sub claim, is ignored, and the user sees the sign-out prompt. If your ID tokens have a custom typ header, add it to IdentityServerOptions.IdentityTokenJwtTypes.IServerSideTicketStore with your own implementation, upgrading doesn't fix the vulnerability for you; see the advisory for the change to make.DefaultDPoPProofValidator.ValidateSignatureAsync, replaced the Handler of JwtRequestValidator, or registered your own secret validator for client assertions, see the advisory for what your code must check.Full Changelog: is-7.3.5...is-7.3.6
This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 7.3.x users upgrad
This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 7.3.x users upgrade.
client_id does not exactly match the authenticated client, as required by RFC 9126. Custom IPushedAuthorizationRequestValidator implementations remain responsible for enforcing this binding.AllowUnregisteredPushedRedirectUris. These clients do not authenticate at the PAR endpoint, so they must register their redirect URIs.AllowUnregisteredPushedRedirectUris is enabled, unregistered redirect URIs must now use the https scheme and must not match ValidationOptions.InvalidRedirectUriPrefixes. Registered redirect URIs, loopback handling, and custom redirect URI validators are unchanged.https PAR redirect URIs (for example http://localhost during local development) must be registered or moved to https.Full Changelog: is-7.3.4...is-7.3.5
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
If you replaced IServerSideTicketStore with your own implementation, upgrading doesn't fix the vulnerability for you; see the advisory for the change…
We've published several security advisories for Duende products including IdentityServer and BFF, along with updated packages that fix them. We strongly recommend updating to the latest patched releases.
The same fixes are released in 8.0.11, 7.4.15, 7.3.6, 7.2.6, 7.1.4 and 7.0.11.
AddMutualTlsSecretValidators(), make sure the certificate authentication scheme (MutualTls.ClientCertificateAuthenticationScheme, Certificate by default) is registered, usually with AddCertificate(). Clients with a thumbprint (X509Thumbprint) secret that present a self-signed certificate keep working only if AllowedCertificateTypes includes CertificateTypes.SelfSigned. Clients that use a self-signed certificate with a subject name (X509Name) secret must switch to a thumbprint secret or a CA-issued certificate.id_token_hint that isn't an ID token, or that has no sub claim, is ignored, and the user sees the sign-out prompt. If your ID tokens have a custom typ header, add it to IdentityServerOptions.IdentityTokenJwtTypes.IServerSideTicketStore with your own implementation, upgrading doesn't fix the vulnerability for you; see the advisory for the change to make.DefaultDPoPProofValidator.ValidateSignatureAsync, replaced the Handler of JwtRequestValidator, or registered your own secret validator for client assertions, see the advisory for what your code must check.Full Changelog: is-7.2.5...is-7.2.6
This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 7.2.x users upgrad
This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 7.2.x users upgrade.
client_id does not exactly match the authenticated client, as required by RFC 9126. Custom IPushedAuthorizationRequestValidator implementations remain responsible for enforcing this binding.AllowUnregisteredPushedRedirectUris. These clients do not authenticate at the PAR endpoint, so they must register their redirect URIs.AllowUnregisteredPushedRedirectUris is enabled, unregistered redirect URIs must now use the https scheme and must not match ValidationOptions.InvalidRedirectUriPrefixes. Registered redirect URIs, loopback handling, and custom redirect URI validators are unchanged.https PAR redirect URIs (for example http://localhost during local development) must be registered or moved to https.Full Changelog: is-7.2.4...is-7.2.5
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
If you replaced IServerSideTicketStore with your own implementation, upgrading doesn't fix the vulnerability for you; see the advisory for the change…
We've published several security advisories for Duende products including IdentityServer and BFF, along with updated packages that fix them. We strongly recommend updating to the latest patched releases.
The same fixes are released in 8.0.11, 7.4.15, 7.3.6, 7.2.6, 7.1.4 and 7.0.11.
AddMutualTlsSecretValidators(), make sure the certificate authentication scheme (MutualTls.ClientCertificateAuthenticationScheme, Certificate by default) is registered, usually with AddCertificate(). Clients with a thumbprint (X509Thumbprint) secret that present a self-signed certificate keep working only if AllowedCertificateTypes includes CertificateTypes.SelfSigned. Clients that use a self-signed certificate with a subject name (X509Name) secret must switch to a thumbprint secret or a CA-issued certificate.id_token_hint that isn't an ID token, or that has no sub claim, is ignored, and the user sees the sign-out prompt. If your ID tokens have a custom typ header, add it to IdentityServerOptions.IdentityTokenJwtTypes.IServerSideTicketStore with your own implementation, upgrading doesn't fix the vulnerability for you; see the advisory for the change to make.DefaultDPoPProofValidator.ValidateSignatureAsync, replaced the Handler of JwtRequestValidator, or registered your own secret validator for client assertions, see the advisory for what your code must check.Full Changelog: is-7.1.3...is-7.1.4
This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 7.1.x users upgrad
This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 7.1.x users upgrade.
client_id does not exactly match the authenticated client, as required by RFC 9126. Custom IPushedAuthorizationRequestValidator implementations remain responsible for enforcing this binding.AllowUnregisteredPushedRedirectUris. These clients do not authenticate at the PAR endpoint, so they must register their redirect URIs.AllowUnregisteredPushedRedirectUris is enabled, unregistered redirect URIs must now use the https scheme and must not match ValidationOptions.InvalidRedirectUriPrefixes. Registered redirect URIs, loopback handling, and custom redirect URI validators are unchanged.https PAR redirect URIs (for example http://localhost during local development) must be registered or moved to https.Full Changelog: is-7.1.1...is-7.1.3
Nothing published for this version
Pre-release Pre-release Compare
Pre-release
Pre-release
Compare
If you replaced IServerSideTicketStore with your own implementation, upgrading doesn't fix the vulnerability for you; see the advisory for the change…
We've published several security advisories for Duende products including IdentityServer and BFF, along with updated packages that fix them. We strongly recommend updating to the latest patched releases.
The same fixes are released in 8.0.11, 7.4.15, 7.3.6, 7.2.6, 7.1.4 and 7.0.11.
AddMutualTlsSecretValidators(), make sure the certificate authentication scheme (MutualTls.ClientCertificateAuthenticationScheme, Certificate by default) is registered, usually with AddCertificate(). Clients with a thumbprint (X509Thumbprint) secret that present a self-signed certificate keep working only if AllowedCertificateTypes includes CertificateTypes.SelfSigned. Clients that use a self-signed certificate with a subject name (X509Name) secret must switch to a thumbprint secret or a CA-issued certificate.id_token_hint that isn't an ID token, or that has no sub claim, is ignored, and the user sees the sign-out prompt. If your ID tokens have a custom typ header, add it to IdentityServerOptions.IdentityTokenJwtTypes.IServerSideTicketStore with your own implementation, upgrading doesn't fix the vulnerability for you; see the advisory for the change to make.DefaultDPoPProofValidator.ValidateSignatureAsync, replaced the Handler of JwtRequestValidator, or registered your own secret validator for client assertions, see the advisory for what your code must check.Full Changelog: is-7.0.10...is-7.0.11
This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 7.0.x users upgrad
This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 7.0.x users upgrade.
client_id does not exactly match the authenticated client, as required by RFC 9126. Custom IPushedAuthorizationRequestValidator implementations remain responsible for enforcing this binding.AllowUnregisteredPushedRedirectUris. These clients do not authenticate at the PAR endpoint, so they must register their redirect URIs.AllowUnregisteredPushedRedirectUris is enabled, unregistered redirect URIs must now use the https scheme and must not match ValidationOptions.InvalidRedirectUriPrefixes. Registered redirect URIs, loopback handling, and custom redirect URI validators are unchanged.https PAR redirect URIs (for example http://localhost during local development) must be registered or moved to https.Full Changelog: f28cac9...is-7.0.10
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.