Repository navigation
Bump the duende group with 4 updates - #1098
Open
dependabot[bot] wants to merge 12 commits into
Open
dependabot[bot] wants to merge 12 commits into
dependabot[bot] wants to merge 12 commits into
Conversation
Bumps Duende.IdentityServer from 7.3.2 to 8.0.11 Bumps Duende.IdentityServer.AspNetIdentity from 7.3.2 to 8.0.11 Bumps Duende.IdentityServer.EntityFramework from 7.3.2 to 8.0.11 Bumps Duende.IdentityServer.Storage from 7.3.2 to 8.0.11 --- updated-dependencies: - dependency-name: Duende.IdentityServer dependency-version: 8.0.11 dependency-type: direct:production update-type: version-update:semver-major dependency-group: duende - dependency-name: Duende.IdentityServer.Storage dependency-version: 8.0.11 dependency-type: direct:production update-type: version-update:semver-major dependency-group: duende - dependency-name: Duende.IdentityServer.AspNetIdentity dependency-version: 8.0.11 dependency-type: direct:production update-type: version-update:semver-major dependency-group: duende - dependency-name: Duende.IdentityServer.EntityFramework dependency-version: 8.0.11 dependency-type: direct:production update-type: version-update:semver-major dependency-group: duende ... Signed-off-by: dependabot[bot] <support@github.com>
* Update to .NET 11 - Target net11.0 across all projects and use SDK 11.0.100 - Update ASP.NET Core, runtime, and dotnet/extensions packages to 11.0.0 - Update Microsoft.OpenApi to 3.11.0 (required by Microsoft.AspNetCore.OpenApi 11) and regenerate Catalog.API OpenAPI documents - Keep EF Core/Npgsql on 10.x until Npgsql and Aspire support EF Core 11 - Update MAUI packages to 11.0.10 and CommunityToolkit.Maui to 17.0.0; drop the unused Maui.Controls.Compatibility package - Remove package references now provided by the framework (NU1510) - Fix new .NET 11 Blazor analyzer warnings and the obsolete EditContext.Validate() Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Address review feedback for MAUI .NET 11 upgrade - Raise ClientApp Android minimum API level to 24 (required by .NET 11) - Migrate obsolete MAUI APIs to DisplayAlertAsync, FadeToAsync, ScaleToAsync Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Fix remaining MAUI 11 obsoletion errors in ClientApp - Remove unused CustomTabbedPage (conflicts with new TabbedPage badge APIs) - Replace UseSafeArea/IgnoreSafeArea with SafeAreaEdges - Replace FillAndExpand with Fill - Remove unused ListView cell styles and ItemTappedEventArgsConverter Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * Update EF Core to 11.0.0-rc.3 with Npgsql EF 11.0.0-rc.3 Npgsql.EntityFrameworkCore.PostgreSQL 11.0.0-rc.3 pins EF Core to exactly 11.0.0-rc.3, so EF Core and Identity.EF move to rc.3 as well. Aspire.Npgsql.EntityFrameworkCore.PostgreSQL 13.x's EnrichNpgsqlDbContext retry setup references NpgsqlExecutionStrategy, which Npgsql 11 removed. Ordering.API now configures EnableRetryOnFailure directly and disables Aspire's retry setup. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Bumps Aspire.Hosting.Azure.AppContainers from 13.6.0 to 13.6.5 Bumps Aspire.Hosting.PostgreSQL from 13.6.0 to 13.6.5 Bumps Aspire.Hosting.RabbitMQ from 13.6.0 to 13.6.5 Bumps Aspire.Hosting.Redis from 13.6.0 to 13.6.5 Bumps Aspire.Hosting.Yarp from 13.6.0 to 13.6.5 Bumps Aspire.Npgsql from 13.6.0 to 13.6.5 Bumps Aspire.Npgsql.EntityFrameworkCore.PostgreSQL from 13.6.0 to 13.6.5 Bumps Aspire.RabbitMQ.Client from 13.6.0 to 13.6.5 Bumps Aspire.StackExchange.Redis from 13.6.0 to 13.6.5 --- updated-dependencies: - dependency-name: Aspire.Hosting.Azure.AppContainers dependency-version: 13.6.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: aspire - dependency-name: Aspire.Hosting.PostgreSQL dependency-version: 13.6.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: aspire - dependency-name: Aspire.Hosting.RabbitMQ dependency-version: 13.6.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: aspire - dependency-name: Aspire.Hosting.Redis dependency-version: 13.6.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: aspire - dependency-name: Aspire.Hosting.Yarp dependency-version: 13.6.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: aspire - dependency-name: Aspire.Npgsql dependency-version: 13.6.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: aspire - dependency-name: Aspire.Npgsql.EntityFrameworkCore.PostgreSQL dependency-version: 13.6.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: aspire - dependency-name: Aspire.RabbitMQ.Client dependency-version: 13.6.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: aspire - dependency-name: Aspire.StackExchange.Redis dependency-version: 13.6.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: aspire ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps Grpc.AspNetCore from 2.84.0 to 2.85.0 Bumps Grpc.Net.ClientFactory from 2.84.0 to 2.85.0 Bumps Grpc.Tools from 2.84.0 to 2.85.0 --- updated-dependencies: - dependency-name: Grpc.AspNetCore dependency-version: 2.85.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: grpc - dependency-name: Grpc.Net.ClientFactory dependency-version: 2.85.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: grpc - dependency-name: Grpc.Tools dependency-version: 2.85.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: grpc ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
--- updated-dependencies: - dependency-name: MSTest.Sdk dependency-version: 4.5.3 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: mstest ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
--- updated-dependencies: - dependency-name: Microsoft.OpenApi dependency-version: 3.11.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
--- updated-dependencies: - dependency-name: NSubstitute dependency-version: 6.2.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…ons (#1104) Bumps FluentValidation from 12.1.1 to 12.2.0 Bumps FluentValidation.DependencyInjectionExtensions from 12.1.1 to 12.2.0 --- updated-dependencies: - dependency-name: FluentValidation dependency-version: 12.2.0 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: FluentValidation.DependencyInjectionExtensions dependency-version: 12.2.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
) --- updated-dependencies: - dependency-name: CommunityToolkit.Aspire.Hosting.Ollama dependency-version: 13.6.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps Duende.IdentityServer from 7.3.2 to 8.0.11 Bumps Duende.IdentityServer.AspNetIdentity from 7.3.2 to 8.0.11 Bumps Duende.IdentityServer.EntityFramework from 7.3.2 to 8.0.11 Bumps Duende.IdentityServer.Storage from 7.3.2 to 8.0.11 --- updated-dependencies: - dependency-name: Duende.IdentityServer dependency-version: 8.0.11 dependency-type: direct:production update-type: version-update:semver-major dependency-group: duende - dependency-name: Duende.IdentityServer.Storage dependency-version: 8.0.11 dependency-type: direct:production update-type: version-update:semver-major dependency-group: duende - dependency-name: Duende.IdentityServer.AspNetIdentity dependency-version: 8.0.11 dependency-type: direct:production update-type: version-update:semver-major dependency-group: duende - dependency-name: Duende.IdentityServer.EntityFramework dependency-version: 8.0.11 dependency-type: direct:production update-type: version-update:semver-major dependency-group: duende ... Signed-off-by: dependabot[bot] <support@github.com>
Align EntityFramework.Storage, migrate identity interactions and request cancellation, and cover login cancellation and diagnostics decoding. Preserve the .NET 11 EF/Npgsql dependency pins. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Retain the existing remote PR head as an ancestor for a normal fast-forward push, preserving the validated Duende 8.0.11 dependency alignment. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated Duende.IdentityServer from 7.3.2 to 8.0.11.
Release notes
Sourced from Duende.IdentityServer's releases.
8.0.11
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.
Security fixes
Upgrade notes
mTLS: if you call
AddMutualTlsSecretValidators(), make sure the certificate authentication scheme (MutualTls.ClientCertificateAuthenticationScheme,Certificateby default) is registered, usually withAddCertificate(). Clients with a thumbprint (X509Thumbprint) secret that present a self-signed certificate keep working only ifAllowedCertificateTypesincludesCertificateTypes.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_hintthat isn't an ID token, or that has nosubclaim, is ignored, and the user sees the sign-out prompt. If your ID tokens have a customtypheader, add it toIdentityServerOptions.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
IServerSideTicketStorewith 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 theHandlerofJwtRequestValidator, 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()), orAddSamlServiceProvider()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 toCaptureExternalLoginContextinPages/ExternalLogin/Callback.cshtml.cs, right after the block that copies thesidclaim:SAML logout and SameSite: if your session cookie uses
SameSite=LaxorSameSite=Strictand an identity provider sends itsLogoutRequestwith the HTTP-POST binding, the logout no longer ends the IdentityServer session. The default,SameSite=None, isn't affected.Other changes
WebApplicationFactory, no longer hangs.Full Changelog: DuendeSoftware/products@is-8.0.10...is-8.0.11
8.0.10
This release moves IdentityServer's dependencies onto the .NET October 2026 security updates, and fixes an exception during access token validation.
Update your .NET runtime
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.Xmlloads 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.
What's changed
Microsoft.IdentityModeldependencies are raised to the October 2026 patched releases.subclaim but no resolvable client is now rejected withinvalid_token, instead of throwing aNullReferenceExceptionduring user activity validation. Tokens without asubclaim, including custom JWTs issued without a client, are unaffected.Upgrade notes
None.
Full Changelog: DuendeSoftware/products@is-8.0.9...is-8.0.10
8.0.9
This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 8.0.x users upgrade.
GHSA-mxv6-xwqj-ww2p
What's changed
client_iddoes not exactly match the authenticated client, as required by RFC 9126. CustomIPushedAuthorizationRequestValidatorimplementations remain responsible for enforcing this binding.AllowUnregisteredPushedRedirectUris. These clients do not authenticate at the PAR endpoint, so they must register their redirect URIs.AllowUnregisteredPushedRedirectUrisis enabled, unregistered redirect URIs must now use thehttpsscheme and must not matchValidationOptions.InvalidRedirectUriPrefixes. Registered redirect URIs, loopback handling, and custom redirect URI validators are unchanged.Upgrade notes
httpsPAR redirect URIs (for examplehttp://localhostduring local development) must be registered or moved tohttps.Full Changelog: DuendeSoftware/products@is-8.0.8...is-8.0.9
8.0.8
Duende IdentityServer 8.0.8
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.
Fixes and improvements
SAML: Adds configurable outbound
AuthnRequestsigning whenIdentityServeracts 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
AddInMemoryClientsandAddInMemorySamlProvidersthat the last call overwrites the first call.8.0.7
What's changed
This is a patch release of IdentityServer that fixes the following issue:
8.0.6
What's changed
This is a patch release of IdentityServer that fixes the following issue:
DiagnosticHostedServicefailed when certain delegate-based options were configured (e.g., dynamic provider path matching)8.0.5
What's changed
This is a patch release of IdentityServer that fixes the following issue:
8.0.4
What's changed
This is a patch release of IdentityServer that adds support for IDP-initiated SSO when IdentityServer acts as a SAML Service Provider.
New features
AddSamlServiceProvider()or dynamic SAML providers), it can now receive unsolicited authentication responses from upstream identity providers. ConfigureAllowUnsolicitedAuthnResponse = trueand setIdpInitiatedCallbackUrlto 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.Breaking changes
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).Bug fixes
8.0.3
What's changed
This is a patch release of identity server that fixes the following issues:
ITokenValidator.ValidateIdentityTokenAsync— theclientIdparameter is now correctly annotated as nullable to match its intended usage.absolute_refresh_token_lifetimeof 0, which represents no expiration.8.0.2
What's changed
AddConfigurationStorewithout a license that includes the Dynamic Identity Providers feature. The EF configuration store registers anIIdentityProviderStoreimplementation, which incorrectly triggered a license check for Dynamic Identity Providers even when the feature was not in use.8.0.1
What's changed
ITokenValidator.ValidateAccessTokenAsync— theexpectedScopeparameter is now correctly annotated asstring?to match its intended usage.8.0.0
Duende IdentityServer 8.0
Duende IdentityServer 8.0 targets .NET 10 and marks a significant milestone for the product.
SAML 2.0 is now a first-class protocol alongside OpenID Connect and OAuth 2.0, enabling enterprise and legacy applications to authenticate against your server without requiring separate infrastructure.
This release also introduces a FAPI 2.0/OAuth 2.1 conformance report to help you verify high-security deployments, and delivers substantial internal modernization - including adoption of .NET 10's HybridCache,
TimeProvider, nullable reference types, and pervasive cancellation token support - resulting in a cleaner, more maintainable foundation going forward.New Features
SAML 2.0 Identity Provider
IdentityServer can now act as a full SAML 2.0 Identity Provider, allowing enterprise and legacy applications that require SAML to authenticate against your server alongside OpenID Connect clients.
It supports:
Your existing login UI requires only a small update to the cancellation path. See the SAML 2.0 documentation.
SAML 2.0 External Authentication
IdentityServer can now federate with external SAML 2.0 Identity Providers, letting you use a third-party SAML IdP as an upstream identity source - the same way you'd add Google or Microsoft Entra ID as an external provider. Configure SAML external providers statically or dynamically using the existing dynamic providers mechanism. See Configuring a SAML external provider.
Financial-Grade Security & Conformance Report
A new
Duende.IdentityServer.ConformanceReportpackage assesses your IdentityServer deployment against OAuth 2.1 and FAPI 2.0 Security Profile specifications and generates an HTML report at a protected endpoint (/_duende/conformance-report). Use it to verify your server is correctly configured for high-security API scenarios. See the Conformance Report documentation.User Management
IdentityServer 8 integrates with Duende User Management which adds user registration, password management, MFA (TOTP, passkeys), account recovery, and more. See the User Management documentation.
Improvements
Token Cleanup Performance - The token cleanup service now uses a more efficient bulk delete strategy when
IOperationalStoreNotificationis not registered, reducing database load in high-throughput deployments. MySQL EF Core provider compatibility for PAR entry cleanup is also restored.Orphaned Grants Revoked on Session Overwrite - When a server-side session is overwritten (for example, when a user signs in again without signing out first), refresh tokens belonging to the prior session are now automatically revoked. This prevents stale grants from accumulating and remaining valid after re-authentication.
Quieter Secret Validation Logging - Expected-failure log entries in client and API secret validation have been downgraded from Error to Debug. This reduces noise in production logs where failed secret lookups are a normal part of the secret hashing comparison process.
Relaxed Audience Validation - Audience validation for private key JWT authentication in strict mode now accepts single-element JSON arrays in addition to scalar string values, improving compatibility with tokens from issuers that always serialize audiences as arrays.
HTTP 303 Redirects - All redirects from IdentityServer's authorization endpoint now unconditionally use HTTP 303 See Other, aligning with the OAuth 2.0 and OpenID Connect specifications and avoiding issues with intermediaries that treat 302 redirects differently.
Unified Authorization Context - SAML and OpenID Connect flows now share the same
IAuthenticationContextabstraction. Your login page can access protocol-specific context - including SAML-specific details such asRequestedAuthnContext- through a single consistent interface.... (truncated)
7.4.15
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.
Security fixes
Upgrade notes
AddMutualTlsSecretValidators(), make sure the certificate authentication scheme (MutualTls.ClientCertificateAuthenticationScheme,Certificateby default) is registered, usually withAddCertificate(). Clients with a thumbprint (X509Thumbprint) secret that present a self-signed certificate keep working only ifAllowedCertificateTypesincludesCertificateTypes.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_hintthat isn't an ID token, or that has nosubclaim, is ignored, and the user sees the sign-out prompt. If your ID tokens have a customtypheader, add it toIdentityServerOptions.IdentityTokenJwtTypes.IServerSideTicketStorewith your own implementation, upgrading doesn't fix the vulnerability for you; see the advisory for the change to make.DefaultDPoPProofValidator.ValidateSignatureAsync, replaced theHandlerofJwtRequestValidator, or registered your own secret validator for client assertions, see the advisory for what your code must check.Other changes
WebApplicationFactory, no longer hangs.Full Changelog: DuendeSoftware/products@is-7.4.14...is-7.4.15
7.4.14
This release moves IdentityServer's dependencies onto the .NET October 2026 security updates, and fixes an exception during access token validation.
Update your .NET runtime
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.
What's changed
subclaim but no resolvable client is now rejected withinvalid_token, instead of throwing during user activity validation. Tokens with neithersubnorclient_id, and valid tokens with a client, are validated as before.Upgrade notes
None.
Full Changelog: DuendeSoftware/products@is-7.4.13...is-7.4.14
7.4.13
This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 7.4.x users upgrade.
GHSA-mxv6-xwqj-ww2p
What's changed
client_iddoes not exactly match the authenticated client, as required by RFC 9126. CustomIPushedAuthorizationRequestValidatorimplementations remain responsible for enforcing this binding.AllowUnregisteredPushedRedirectUris. These clients do not authenticate at the PAR endpoint, so they must register their redirect URIs.AllowUnregisteredPushedRedirectUrisis enabled, unregistered redirect URIs must now use thehttpsscheme and must not matchValidationOptions.InvalidRedirectUriPrefixes. Registered redirect URIs, loopback handling, and custom redirect URI validators are unchanged.Upgrade notes
httpsPAR redirect URIs (for examplehttp://localhostduring local development) must be registered or moved tohttps.Full Changelog: DuendeSoftware/products@is-7.4.12...is-7.4.13
7.4.12
## What's changed
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.
7.4.11
What's changed
This is a patch release of IdentityServer that fixes the following issue:
DiagnosticHostedServicefailed when certain delegate-based options were configured (e.g., dynamic provider path matching)7.4.10
What's changed
This is a patch release of IdentityServer that fixes the following issue:
7.4.9
What's changed
This is a patch release of identity server that fixes the following issue:
Microsoft.Bcl.Memorydependency fornet8.0to resolve .NET 8 runtime failures at discovery and related endpoints.7.4.8
What's changed
This is a patch release of identity server that fixes the following issue:
absolute_refresh_token_lifetimeof 0, which represents no expiration.7.4.7
7.4.6
This is a patch release that fixes two issues in IdentityServer.
What's Changed
7.4.5
This is bugfix release that fixes an issue where + characters are not treated correctly in URL queries.
What's Changed
Full Changelog: DuendeSoftware/products@is-7.4.4...is-7.4.5
7.4.4
This is bugfix release that fixes an issue where specific service registration scenarios would fail due to constructor ambiguity.
What's Changed
Full Changelog: DuendeSoftware/products@is-7.4.3...is-7.4.4
7.4.3
This is bugfix release that fixes an issue where claims in a session would be duplicated.
What's Changed
Full Changelog: DuendeSoftware/products@is-7.4.2...is-7.4.3
7.4.2
This is a patch release that fixes a bug in license verification.
What's Changed
7.4.1
This is a patch release that fixes a bug related to CSP hashes.
What's Changed
7.4.0
IdentityServer 7.4.0 is a significant release that includes:
Since the 7.4.0 release candidate, there have been a few minor changes, including:
Note that
Duende.IdentityServer.EntityFramework.Storagenow depends on Entity Framework Core 9.x in thenet8.0target framework, which should be fully supported on both .NET 8 and .NET 9. .NET 10 projects will use Entity Framework Core 10.x.Breaking Changes
There are no schema changes needed for IdentityServer 7.4.0. Small code changes maybe be required for some users to upgrade.
Duende.IdentityServer.Models.DiscoveryDocumentclass which was publicTelemetry.csas readonlyRemoved the unused
Duende.IdentityServer.Models.DiscoveryDocumentclass which was publicIn the process of internal code cleanup, this unused and unreferenced file was removed. If code was referencing this file, see the linked PR to create a local copy in the code base needing it.
Marked static properties referring to counters in
Telemetry.csasreadonlyIn the process of internal code cleanup, these properties were updated to be marked as
readonly. Code should not have been updating these properties as it would likely change the behavior of the telemetry emitted by IdentityServer. Any code which was updating these properties should instead create its own counters for its specific scenario.Enhancements
PathMatchingCallbacksetting can be used as an alternative to the previously existingPathPrefixoption.DefaultUiLocalsService.cs, delegates to theCookieRequestCultureProviderif it is present and any of the values passed in theui_locales parametermatch a supported UI culture.IUiLocalesServicecan be implemented and registered with DI.CustomParametersproperty toAuthorizeResponseto support adding custom query parameters to the redirect uri. This will typically be used in conjunction with a customIAuthorizeResponseGenerator.ISessionClaimsFilter.FilterToSessionClaimsAsyncwhich comes with a default implementation.... (truncated)
7.4.0-rc.1
This is the first release candidate of IdentityServer 7.4.0. The changes since the last preview release are:
IdentityServer 7.4.0 is a significant release that includes:
Breaking Changes
There are no schema changes needed for IdentityServer 7.4.0. Small code changes maybe be required for some users to upgrade.
Duende.IdentityServer.Models.DiscoveryDocumentclass which was publicTelemetry.csas readonlyRemoved the unused
Duende.IdentityServer.Models.DiscoveryDocumentclass which was publicIn the process of internal code cleanup, this unused and unreferenced file was removed. If code was referencing this file, see the linked PR to create a local copy in the code base needing it.
Marked static properties referring to counters in
Telemetry.csasreadonlyIn the process of internal code cleanup, these properties were updated to be marked as
readonly. Code should not have been updating these properties as it would likely change the behavior of the telemetry emitted by IdentityServer. Any code which was updating these properties should instead create its own counters for its specific scenario.Enhancements
PathMatchingCallbacksetting can be used as an alternative to the previously existingPathPrefixoption.DefaultUiLocalsService.cs, delegates to theCookieRequestCultureProviderif it is present and any of the values passed in theui_locales parametermatch a supported UI culture.IUiLocalesServicecan be implemented and registered with DI.CustomParametersproperty toAuthorizeResponseto support adding custom query parameters to the redirect uri. This will typically be used in conjunction with a customIAuthorizeResponseGenerator.ISessionClaimsFilter.FilterToSessionClaimsAsyncwhich comes with a default implementation.... (truncated)
7.4.0-preview.2
IdentityServer 7.4.0 is a significant release that includes:
Breaking Changes
There are no schema changes needed for IdentityServer 7.4.0. Small code changes maybe be required for some users to upgrade.
Duende.IdentityServer.Models.DiscoveryDocumentclass which was publicTelemetry.csas readonlyRemoved the unused
Duende.IdentityServer.Models.DiscoveryDocumentclass which was publicIn the process of internal code cleanup, this unused and unreferenced file was removed. If code was referencing this file, see the linked PR to create a local copy in the code base needing it.
Marked static properties referring to counters in
Telemetry.csasreadonlyIn the process of internal code cleanup, these properties were updated to be marked as
readonly. Code should not have been updating these properties as it would likely change the behavior of the telemetry emitted by IdentityServer. Any code which was updating these properties should instead create its own counters for its specific scenario.Enhancements
PathMatchingCallbacksetting can be used as an alternative to the previously existingPathPrefixoption.DefaultUiLocalsService.cs, delegates to theCookieRequestCultureProviderif it is present and any of the values passed in theui_locales parametermatch a supported UI culture.IUiLocalesServicecan be implemented and registered with DI.CustomParametersproperty toAuthorizeResponseto support adding custom query parameters to the redirect uri. This will typically be used in conjunction with a customIAuthorizeResponseGenerator.ISessionClaimsFilter.FilterToSessionClaimsAsyncwhich comes with a default implementation.Bug Fixes
... (truncated)
7.4.0-preview.1
NOTE: There were minor issues with this release. There is a Preview 2 package available which should be used instead.
IdentityServer 7.4.0 is a significant release that includes:
Breaking Changes
There are no schema changes needed for IdentityServer 7.4.0. Small code changes maybe be required for some users to upgrade.
Duende.IdentityServer.Models.DiscoveryDocumentclass which was publicTelemetry.csas readonlyRemoved the unused
Duende.IdentityServer.Models.DiscoveryDocumentclass which was publicIn the process of internal code cleanup, this unused and unreferenced file was used. If code was referencing this file, see the linked PR to create a local copy in the code base needing it.
Marked static properties referring to counters in
Telemetry.csasreadonlyIn the process of internal code cleanup, these properties were updated to be marked as
readonly. Code should not have been updating these properties as it would likely change the behavior of the telemetry emitted by IdentityServer. Any code which was updating these properties should instead create its own counters for its specific scenario.Enhancements
PathMatchingCallbacksetting can be used as an alternative to the previously existingPathPrefixoption.DefaultUiLocalsService.cs, delegates to theCookieRequestCultureProviderif it is present and any of the values passed in theui_locales parametermatch a supported UI culture.IUiLocalesServicecan be implemented and registered with DI.CustomParametersproperty toAuthorizeResponseto support adding custom query parameters to the redirect uri. This will typically be used in conjunction with a customIAuthorizeResponseGenerator.ISessionClaimsFilter.FilterToSessionClaimsAsyncwhich comes with a default implementation.Bug Fixes
... (truncated)
7.3.6
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.
Security fixes
Upgrade notes
AddMutualTlsSecretValidators(), make sure the certificate authentication scheme (MutualTls.ClientCertificateAuthenticationScheme,Certificateby default) is registered, usually withAddCertificate(). Clients with a thumbprint (X509Thumbprint) secret that present a self-signed certificate keep working only ifAllowedCertificateTypesincludesCertificateTypes.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_hintthat isn't an ID token, or that has nosubclaim, is ignored, and the user sees the sign-out prompt. If your ID tokens have a customtypheader, add it toIdentityServerOptions.IdentityTokenJwtTypes.IServerSideTicketStorewith your own implementation, upgrading doesn't fix the vulnerability for you; see the advisory for the change to make.DefaultDPoPProofValidator.ValidateSignatureAsync, replaced theHandlerofJwtRequestValidator, or registered your own secret validator for client assertions, see the advisory for what your code must check.Full Changelog: DuendeSoftware/products@is-7.3.5...is-7.3.6
7.3.5
This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 7.3.x users upgrade.
GHSA-mxv6-xwqj-ww2p
What's changed
client_iddoes not exactly match the authenticated client, as required by RFC 9126. CustomIPushedAuthorizationRequestValidatorimplementations remain responsible for enforcing this binding.AllowUnregisteredPushedRedirectUris. These clients do not authenticate at the PAR endpoint, so they must register their redirect URIs.AllowUnregisteredPushedRedirectUrisis enabled, unregistered redirect URIs must now use thehttpsscheme and must not matchValidationOptions.InvalidRedirectUriPrefixes. Registered redirect URIs, loopback handling, and custom redirect URI validators are unchanged.Upgrade notes
httpsPAR redirect URIs (for examplehttp://localhostduring local development) must be registered or moved tohttps.Full Changelog: DuendeSoftware/products@is-7.3.4...is-7.3.5
7.3.4
This is bugfix release that fixes an issue where specific service registration scenarios would fail due to constructor ambiguity.
What's Changed
Full Changelog: DuendeSoftware/products@is-7.3.3...is-7.3.4
7.3.3
This is a minor release which changes how a CSP hash is calculated to prevent future issues and updates the version of
Duende.IdentityModelused to 8.0.0.What's Changed
Breaking Changes
The update to
Duende.IdentityModelcan cause breaking changes as it is a major version. Refer to the Duende.IdentityModel 8.0.0 release notes for upgrade instructions.Commits viewable in compare view.
Updated Duende.IdentityServer.AspNetIdentity from 7.3.2 to 8.0.11.
Release notes
Sourced from Duende.IdentityServer.AspNetIdentity's releases.
8.0.11
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.
Security fixes
Upgrade notes
mTLS: if you call
AddMutualTlsSecretValidators(), make sure the certificate authentication scheme (MutualTls.ClientCertificateAuthenticationScheme,Certificateby default) is registered, usually withAddCertificate(). Clients with a thumbprint (X509Thumbprint) secret that present a self-signed certificate keep working only ifAllowedCertificateTypesincludesCertificateTypes.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_hintthat isn't an ID token, or that has nosubclaim, is ignored, and the user sees the sign-out prompt. If your ID tokens have a customtypheader, add it toIdentityServerOptions.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
IServerSideTicketStorewith 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 theHandlerofJwtRequestValidator, 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()), orAddSamlServiceProvider()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 toCaptureExternalLoginContextinPages/ExternalLogin/Callback.cshtml.cs, right after the block that copies thesidclaim:SAML logout and SameSite: if your session cookie uses
SameSite=LaxorSameSite=Strictand an identity provider sends itsLogoutRequestwith the HTTP-POST binding, the logout no longer ends the IdentityServer session. The default,SameSite=None, isn't affected.Other changes
WebApplicationFactory, no longer hangs.Full Changelog: DuendeSoftware/products@is-8.0.10...is-8.0.11
8.0.10
This release moves IdentityServer's dependencies onto the .NET October 2026 security updates, and fixes an exception during access token validation.
Update your .NET runtime
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.Xmlloads 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.
What's changed
Microsoft.IdentityModeldependencies are raised to the October 2026 patched releases.subclaim but no resolvable client is now rejected withinvalid_token, instead of throwing aNullReferenceExceptionduring user activity validation. Tokens without asubclaim, including custom JWTs issued without a client, are unaffected.Upgrade notes
None.
Full Changelog: DuendeSoftware/products@is-8.0.9...is-8.0.10
8.0.9
This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 8.0.x users upgrade.
GHSA-mxv6-xwqj-ww2p
What's changed
client_iddoes not exactly match the authenticated client, as required by RFC 9126. CustomIPushedAuthorizationRequestValidatorimplementations remain responsible for enforcing this binding.AllowUnregisteredPushedRedirectUris. These clients do not authenticate at the PAR endpoint, so they must register their redirect URIs.AllowUnregisteredPushedRedirectUrisis enabled, unregistered redirect URIs must now use thehttpsscheme and must not matchValidationOptions.InvalidRedirectUriPrefixes. Registered redirect URIs, loopback handling, and custom redirect URI validators are unchanged.Upgrade notes
httpsPAR redirect URIs (for examplehttp://localhostduring local development) must be registered or moved tohttps.Full Changelog: DuendeSoftware/products@is-8.0.8...is-8.0.9
8.0.8
Duende IdentityServer 8.0.8
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.
Fixes and improvements
SAML: Adds configurable outbound
AuthnRequestsigning whenIdentityServeracts 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
AddInMemoryClientsandAddInMemorySamlProvidersthat the last call overwrites the first call.8.0.7
What's changed
This is a patch release of IdentityServer that fixes the following issue:
8.0.6
What's changed
This is a patch release of IdentityServer that fixes the following issue:
DiagnosticHostedServicefailed when certain delegate-based options were configured (e.g., dynamic provider path matching)8.0.5
What's changed
This is a patch release of IdentityServer that fixes the following issue:
8.0.4
What's changed
This is a patch release of IdentityServer that adds support for IDP-initiated SSO when IdentityServer acts as a SAML Service Provider.
New features
AddSamlServiceProvider()or dynamic SAML providers), it can now receive unsolicited authentication responses from upstream identity providers. ConfigureAllowUnsolicitedAuthnResponse = trueand setIdpInitiatedCallbackUrlto 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.Breaking changes
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).Bug fixes
8.0.3
What's changed
This is a patch release of identity server that fixes the following issues:
ITokenValidator.ValidateIdentityTokenAsync— theclientIdparameter is now correctly annotated as nullable to match its intended usage.absolute_refresh_token_lifetimeof 0, which represents no expiration.8.0.2
What's changed
AddConfigurationStorewithout a license that includes the Dynamic Identity Providers feature. The EF configuration store registers anIIdentityProviderStoreimplementation, which incorrectly triggered a license check for Dynamic Identity Providers even when the feature was not in use.8.0.1
What's changed
ITokenValidator.ValidateAccessTokenAsync— theexpectedScopeparameter is now correctly annotated asstring?to match its intended usage.8.0.0
Duende IdentityServer 8.0
Duende IdentityServer 8.0 targets .NET 10 and marks a significant milestone for the product.
SAML 2.0 is now a first-class protocol alongside OpenID Connect and OAuth 2.0, enabling enterprise and legacy applications to authenticate against your server without requiring separate infrastructure.
This release also introduces a FAPI 2.0/OAuth 2.1 conformance report to help you verify high-security deployments, and delivers substantial internal modernization - including adoption of .NET 10's HybridCache,
TimeProvider, nullable reference types, and pervasiv...Description has been truncated