Skip to content

Bump the other group with 19 updates - #11

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/dot-config/other-4b53f3f4f2
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/dot-config/other-4b53f3f4f2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 14, 2026

Copy link
Copy Markdown
Contributor

Updated dotnet-ef from 8.0.31 to 8.0.34.

Release notes

Sourced from dotnet-ef's releases.

8.0.34

Release

What's Changed

Full Changelog: dotnet/efcore@v8.0.32...v8.0.34

8.0.33

Release

Full Changelog: dotnet/efcore@v8.0.32...v8.0.33

8.0.32

Release

What's Changed

Full Changelog: dotnet/efcore@v8.0.31...v8.0.32

Commits viewable in compare view.

Updated dotnet-reportgenerator-globaltool from 5.5.11 to 5.6.0.

Release notes

Sourced from dotnet-reportgenerator-globaltool's releases.

5.6.0

Changes:

This release requires .NET Framework 4.7 or .NET 8.0/9.0/10.0/11.0

5.5.12

Changes:

  • #​790 Allow a custom file reader for the source files when generating a report (contributed by @​jeremy-morren)

This release requires .NET Framework 4.7 or .NET 8.0/9.0/10.0

Commits viewable in compare view.

Updated Duende.IdentityServer.AspNetIdentity from 7.0.0 to 7.4.14.

Release notes

Sourced from Duende.IdentityServer.AspNetIdentity's releases.

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:

  • Kestrel: HTTP/1 request smuggling (CVE-2026-88092) and HTTP/2 header handling (CVE-2026-70188), both critical.
  • Request parsing: denial-of-service fixes for form and multipart parsing (CVE-2026-70181, CVE-2026-70196), which IdentityServer's protocol endpoints use for unauthenticated form posts.
  • ASP.NET Core Identity: password reset and confirmation emails now go to the user's stored address (CVE-2026-70175). If your login UI implements its own reset flow, check that it does the same.

See Microsoft's .NET security announcements for the full list.

What's changed

  • Dependencies: the minimum versions of the ASP.NET Core dependencies are raised to the October 2026 patched releases.
  • Access token validation: a JWT access token that has a 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.

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

  • PAR: Pushed authorization requests are now rejected when the request's client_id does not exactly match the authenticated client, as required by RFC 9126. Custom IPushedAuthorizationRequestValidator implementations remain responsible for enforcing this binding.
  • PAR: Implicit-only clients can no longer use AllowUnregisteredPushedRedirectUris. These clients do not authenticate at the PAR endpoint, so they must register their redirect URIs.
  • PAR: When 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.

Upgrade notes

  • Implicit-only clients that relied on unregistered pushed redirect URIs must register those redirect URIs.
  • Unregistered non-https PAR redirect URIs (for example http://localhost during local development) must be registered or moved to https.

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:

  • Validation failures from bad external input: Lowered from Error to Information for malformed requests (e.g., authorize and token endpoints), ensuring expected client-side errors no longer trigger error-level alerts.

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:

  • The DiagnosticHostedService failed 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:

  • Fixed an InvalidCastException that could occur during server-side session cleanup. When a concurrent deletion caused a DbUpdateConcurrencyException in PersistedGrantStore.RemoveAllAsync, the affected entries were not detached from the EF Core change tracker. Those stale entries could then cause type mismatches in subsequent save operations. The fix ensures entries are properly detached after a concurrency exception.

7.4.9

What's changed

This is a patch release of identity server that fixes the following issue:

  • Added a direct Microsoft.Bcl.Memory dependency for net8.0 to 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:

  • Fixed Dynamic Client Registration to allow absolute_refresh_token_lifetime of 0, which represents no expiration.

7.4.7

  • Update Duende.IdentityModel dependency to 8.0.1

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:

  • Support for .NET 10
  • Support for OAuth 2.0 Authorization Server Metadata (RFC 8414)
  • New Callback option for path detection in Dynamic Providers
  • Improved UI locales support
  • Support for custom parameters in the Authorize Redirect Uri
  • Identity package now persists session claims based on an interface
  • Skipping front-channel logout iframe when unnecessary
  • Set HTTP activity name on routing

Since the 7.4.0 release candidate, there have been a few minor changes, including:

  • Add service for diagnostic data by @​josephdecock in #​2252
  • Trigger Back Channel Logout Earlier in Pipeline by @​bhazen in #​2258
  • Enable Customizing ErrorMessage on Redirect to Error Page by @​bhazen in #​2263
  • Better DCR Support for Public Clientsby @​bhazen in #​2264
  • Update .NET 10 from Release Candidate to GA by @​pgermishuys in #​2267

Note that Duende.IdentityServer.EntityFramework.Storage now depends on Entity Framework Core 9.x in the net8.0 target 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.

  • Removed the unused Duende.IdentityServer.Models.DiscoveryDocument class which was public
  • Marked static properties referring to counters in Telemetry.cs as readonly

Removed the unused Duende.IdentityServer.Models.DiscoveryDocument class which was public

  • Address CA1707 violations by @​bhazen in #​2128
    In 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.cs as readonly

  • Address CA2211 Violations by @​bhazen in #​2170
    In 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

  • Set HTTP activity name on routing by @​josephdecock in #​2049
    • Set the DisplayName of the activity associated with the incoming HttpRequest when IdentityServer routes are matched. This makes the IdentityServer route names appear in OTel traces.
  • Skip front-channel logout iframe when unnecessary by @​bhazen in #​2109
    • Enables the UI to skip rendering the front channel logout iframe when it is not needed.
  • Callback Option for Path Detection in Dynamic Providers by @​bhazen in #​2126
    • Adds a new option for Dynamic Providers to increase flexibility when routing to dynamic providers. The new PathMatchingCallback setting can be used as an alternative to the previously existing PathPrefix option.
  • Improved UI locales support by @​bhazen in #​2158
    • Improves support for the ui_locales parameter in protocol request which support it to allow for better localization.
    • The default implementation, DefaultUiLocalsService.cs, delegates to the CookieRequestCultureProvider if it is present and any of the values passed in the ui_locales parameter match a supported UI culture.
    • If the default implementation does not meet your needs, IUiLocalesService can be implemented and registered with DI.
  • RFC 8414 support by @​bhazen in #​2189
    • Adds out of box support for OAuth 2.0 Authorization Server Metadata as defined in RFC 8414
  • Support for custom parameters in authorize response by @​bhazen in #​2206
    • Adds a new CustomParameters property to AuthorizeResponse to support adding custom query parameters to the redirect uri. This will typically be used in conjunction with a custom IAuthorizeResponseGenerator.
  • Use Customizable Filter to Persist Session Claims in ASP.NET Identity by @​bhazen in #​2213
    • The ASP.NET Identity integration package now persists session claims based on ISessionClaimsFilter.FilterToSessionClaimsAsync which 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:

  • Add service for diagnostic data by @​josephdecock in #​2252
  • Trigger Back Channel Logout Earlier in Pipeline by @​bhazen in #​2258
  • Enable Customizing ErrorMessage on Redirect to Error Page by @​bhazen in #​2263
  • Better DCR Support for Public Clientsby @​bhazen in #​2264
  • Update .NET 10 from Release Candidate to GA by @​pgermishuys in #​2267

IdentityServer 7.4.0 is a significant release that includes:

  • Support for .NET 10 (this preview targets .NET10 RC2)
  • Support for OAuth 2.0 Authorization Server Metadata (RFC 8414)
  • New Callback option for path detection in Dynamic Providers
  • Improved UI locales support
  • Support for custom parameters in the Authorize Redirect Uri
  • Identity package now persists session claims based on an interface
  • Skipping front-channel logout iframe when unnecessary
  • Set HTTP activity name on routing

Breaking Changes

There are no schema changes needed for IdentityServer 7.4.0. Small code changes maybe be required for some users to upgrade.

  • Removed the unused Duende.IdentityServer.Models.DiscoveryDocument class which was public
  • Marked static properties referring to counters in Telemetry.cs as readonly

Removed the unused Duende.IdentityServer.Models.DiscoveryDocument class which was public

  • Address CA1707 violations by @​bhazen in #​2128
    In 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.cs as readonly

  • Address CA2211 Violations by @​bhazen in #​2170
    In 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

  • Set HTTP activity name on routing by @​josephdecock in #​2049
    • Set the DisplayName of the activity associated with the incoming HttpRequest when IdentityServer routes are matched. This makes the IdentityServer route names appear in OTel traces.
  • Skip front-channel logout iframe when unnecessary by @​bhazen in #​2109
    • Enables the UI to skip rendering the front channel logout iframe when it is not needed.
  • Callback Option for Path Detection in Dynamic Providers by @​bhazen in #​2126
    • Adds a new option for Dynamic Providers to increase flexibility when routing to dynamic providers. The new PathMatchingCallback setting can be used as an alternative to the previously existing PathPrefix option.
  • Improved UI locales support by @​bhazen in #​2158
    • Improves support for the ui_locales parameter in protocol request which support it to allow for better localization.
    • The default implementation, DefaultUiLocalsService.cs, delegates to the CookieRequestCultureProvider if it is present and any of the values passed in the ui_locales parameter match a supported UI culture.
    • If the default implementation does not meet your needs, IUiLocalesService can be implemented and registered with DI.
  • RFC 8414 support by @​bhazen in #​2189
    • Adds out of box support for OAuth 2.0 Authorization Server Metadata as defined in RFC 8414
  • Support for custom parameters in authorize response by @​bhazen in #​2206
    • Adds a new CustomParameters property to AuthorizeResponse to support adding custom query parameters to the redirect uri. This will typically be used in conjunction with a custom IAuthorizeResponseGenerator.
  • Use Customizable Filter to Persist Session Claims in ASP.NET Identity by @​bhazen in #​2213
    • The ASP.NET Identity integration package now persists session claims based on ISessionClaimsFilter.FilterToSessionClaimsAsync which comes with a default implementation.
    • The new interface can be implemented to customize which session claims are persisted in non-default scenarios.
  • .NET 10 Support (Simplified) by @​josephdecock in #​2216
    ... (truncated)

7.4.0-preview.2

IdentityServer 7.4.0 is a significant release that includes:

  • Support for .NET 10 (this preview targets .NET10 RC2)
  • Support for OAuth 2.0 Authorization Server Metadata (RFC 8414)
  • New Callback option for path detection in Dynamic Providers
  • Improved UI locales support
  • Support for custom parameters in the Authorize Redirect Uri
  • Identity package now persists session claims based on an interface
  • Skipping front-channel logout iframe when unnecessary
  • Set HTTP activity name on routing

Breaking Changes

There are no schema changes needed for IdentityServer 7.4.0. Small code changes maybe be required for some users to upgrade.

  • Removed the unused Duende.IdentityServer.Models.DiscoveryDocument class which was public
  • Marked static properties referring to counters in Telemetry.cs as readonly

Removed the unused Duende.IdentityServer.Models.DiscoveryDocument class which was public

  • Address CA1707 violations by @​bhazen in #​2128
    In 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.cs as readonly

  • Address CA2211 Violations by @​bhazen in #​2170
    In 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

  • Set HTTP activity name on routing by @​josephdecock in #​2049
    • Set the DisplayName of the activity associated with the incoming HttpRequest when IdentityServer routes are matched. This makes the IdentityServer route names appear in OTel traces.
  • Skip front-channel logout iframe when unnecessary by @​bhazen in #​2109
    • Enables the UI to skip rendering the front channel logout iframe when it is not needed.
  • Callback Option for Path Detection in Dynamic Providers by @​bhazen in #​2126
    • Adds a new option for Dynamic Providers to increase flexibility when routing to dynamic providers. The new PathMatchingCallback setting can be used as an alternative to the previously existing PathPrefix option.
  • Improved UI locales support by @​bhazen in #​2158
    • Improves support for the ui_locales parameter in protocol request which support it to allow for better localization.
    • The default implementation, DefaultUiLocalsService.cs, delegates to the CookieRequestCultureProvider if it is present and any of the values passed in the ui_locales parameter match a supported UI culture.
    • If the default implementation does not meet your needs, IUiLocalesService can be implemented and registered with DI.
  • RFC 8414 support by @​bhazen in #​2189
    • Adds out of box support for OAuth 2.0 Authorization Server Metadata as defined in RFC 8414
  • Support for custom parameters in authorize response by @​bhazen in #​2206
    • Adds a new CustomParameters property to AuthorizeResponse to support adding custom query parameters to the redirect uri. This will typically be used in conjunction with a custom IAuthorizeResponseGenerator.
  • Use Customizable Filter to Persist Session Claims in ASP.NET Identity by @​bhazen in #​2213
    • The ASP.NET Identity integration package now persists session claims based on ISessionClaimsFilter.FilterToSessionClaimsAsync which comes with a default implementation.
    • The new interface can be implemented to customize which session claims are persisted in non-default scenarios.
  • .NET 10 Support (Simplified) by @​josephdecock in #​2216
    • Added initial support for .NET 10.
  • Updated IS and BFF to IM 8.0.0 Preview 1 and ATM Previews in #​2247

Bug Fixes

  • Reject Pushed Authorization Requests with parameters duplicated in a JAR by @​wcabus in #​2073
    • Fixes a bug where when posting a PAR containing the "request" request parameter other requests parameters were being allowed.
    • Such as request will now correctly return an invalid request.
      ... (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:

  • Support for .NET 10 (this preview targets .NET10 RC2)
  • Support for OAuth 2.0 Authorization Server Metadata (RFC 8414)
  • New Callback option for path detection in Dynamic Providers
  • Improved UI locales support
  • Support for custom parameters in the Authorize Redirect Uri
  • Identity package now persists session claims based on an interface
  • Skipping front-channel logout iframe when unnecessary
  • Set HTTP activity name on routing

Breaking Changes

There are no schema changes needed for IdentityServer 7.4.0. Small code changes maybe be required for some users to upgrade.

  • Removed the unused Duende.IdentityServer.Models.DiscoveryDocument class which was public
  • Marked static properties referring to counters in Telemetry.cs as readonly

Removed the unused Duende.IdentityServer.Models.DiscoveryDocument class which was public

  • Address CA1707 violations by @​bhazen in #​2128
    In 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.cs as readonly

  • Address CA2211 Violations by @​bhazen in #​2170
    In 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

  • Set HTTP activity name on routing by @​josephdecock in #​2049
    • Set the DisplayName of the activity associated with the incoming HttpRequest when IdentityServer routes are matched. This makes the IdentityServer route names appear in OTel traces.
  • Skip front-channel logout iframe when unnecessary by @​bhazen in #​2109
    • Enables the UI to skip rendering the front channel logout iframe when it is not needed.
  • Callback Option for Path Detection in Dynamic Providers by @​bhazen in #​2126
    • Adds a new option for Dynamic Providers to increase flexibility when routing to dynamic providers. The new PathMatchingCallback setting can be used as an alternative to the previously existing PathPrefix option.
  • Improved UI locales support by @​bhazen in #​2158
    • Improves support for the ui_locales parameter in protocol request which support it to allow for better localization.
    • The default implementation, DefaultUiLocalsService.cs, delegates to the CookieRequestCultureProvider if it is present and any of the values passed in the ui_locales parameter match a supported UI culture.
    • If the default implementation does not meet your needs, IUiLocalesService can be implemented and registered with DI.
  • RFC 8414 support by @​bhazen in #​2189
    • Adds out of box support for OAuth 2.0 Authorization Server Metadata as defined in RFC 8414
  • Support for custom parameters in authorize response by @​bhazen in #​2206
    • Adds a new CustomParameters property to AuthorizeResponse to support adding custom query parameters to the redirect uri. This will typically be used in conjunction with a custom IAuthorizeResponseGenerator.
  • Use Customizable Filter to Persist Session Claims in ASP.NET Identity by @​bhazen in #​2213
    • The ASP.NET Identity integration package now persists session claims based on ISessionClaimsFilter.FilterToSessionClaimsAsync which comes with a default implementation.
    • The new interface can be implemented to customize which session claims are persisted in non-default scenarios.
  • .NET 10 Support (Simplified) by @​josephdecock in #​2216
    • Added initial support for .NET 10.

Bug Fixes

  • Reject Pushed Authorization Requests with parameters duplicated in a JAR by @​wcabus in #​2073
    • Fixes a bug where when posting a PAR containing the "request" request parameter other requests parameters were being allowed.
      ... (truncated)

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

  • PAR: Pushed authorization requests are now rejected when the request's client_id does not exactly match the authenticated client, as required by RFC 9126. Custom IPushedAuthorizationRequestValidator implementations remain responsible for enforcing this binding.
  • PAR: Implicit-only clients can no longer use AllowUnregisteredPushedRedirectUris. These clients do not authenticate at the PAR endpoint, so they must register their redirect URIs.
  • PAR: When 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.

Upgrade notes

  • Implicit-only clients that relied on unregistered pushed redirect URIs must register those redirect URIs.
  • Unregistered non-https PAR redirect URIs (for example http://localhost during local development) must be registered or moved to https.

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.IdentityModel used to 8.0.0.

What's Changed

  • Resolve CSP by moving it to a not dotnet formattable file by @​pgermishuys in #​2295
  • Updated to IdentityModel 8.0.0 by @​bhazen in #​2302

Breaking Changes

The update to Duende.IdentityModel can cause breaking changes as it is a major version. Refer to the Duende.IdentityModel 8.0.0 release notes for upgrade instructions.

7.3.2

This is a patch release that optimizes key creation when not using X509 Certificates.

Details

  • Do not unnecessarily request current issuer when creating new key

7.3.1

This is a patch release that fixes a bug and enables a System.Text.Json serialization option.

Details

  • Fixed an issue where uncommon license features caused an exception.
  • Allow RespectNullableAnnotationsDefault to be globally enabled. This is a relatively new feature in System.Text.Json that can be globally opted in to.

7.3.0

IdentityServer 7.3.0 is a significant release that includes:

  • FAPI 2.0 profile certification
  • JWT Response from the introspection endpoint (RFC 9701)
  • Diagnostic data
  • Removal of the experimental label from OpenTelemetry metrics
  • Additional license compliance warnings
  • Several bug fixes
  • Numerous small code quality and performance enhancements from the community

Breaking Changes

There are no schema changes needed for IdentityServer 7.3.0. Small code changes maybe be required for some users to upgrade.

  • The SendLogoutNotificationAsync method has been removed from the DefaultBackChannelLogoutService class
  • Client Secret is now required for Clients with ClientCredentials Grant

The SendLogoutNotificationAsync method has been removed from the DefaultBackChannelLogoutService class

  • Fix Concurrent DbContext Access on Back Channel Logout by @​bhazen in Fix Concurrent DbContext Access on Back Channel Logout DuendeSoftware/products#2019
    To fix a bug where when using EntityFramework, code which previously executed in parallel needed to be modified to execute sequentially. This necessitated the removal of the SendLogoutNotificationAsync method in the DefaultBackChannelLogoutService class. Anyone who had previously overridden the SendLogoutNotificationAsync as an extensibility point will likely need to move their customization to the PostLogoutJwt method.

Client Secret is now required for Clients with ClientCredentials Grant

  • Ensure Client Secret is Required for Clients with ClientCredentials Grant by @​bhazen in Ensure Client Secret is Required for Clients with ClientCredentials Grant DuendeSoftware/products#1796
    Previously, it was possible to configure a Client to allow the ClientCredentials Grant without requiring a client secret which is undesirable. The default validation of Clients has been updated to ensure any Client which allows the ClientCredentials grant also sets the RequireClientSecret flag to true to disallow the configuration of a private client to behave like a public client.

Enhancements

FAPI 2.0 Profile Certification

IdentityServer is 7.3.0 is officially certified as conformant with the FAPI 2.0 Security Profile.

JWT Response from Introspection Endpoint

IdentityServer now supports RFC 9701 to return a JWT Response from the Introspection endpoint.

Diagnostic Data

Diagnostic data has been added to IdentityServer to help support with troubleshooting. Read more about this new feature in our docs. TODO: link to docs

7.3.0-rc.2

This is the second release candidate for IdentityServer 7.3.0, containing several bug fixes from 7.2 releases that were missed in the first release candidate, as well as editorial changes to some new log messages.

Detailed change log

Previously fixed bugs

Log messages

7.3.0-rc.1

This is release candidate 1 of IdentityServer 7.3.0, a significant release that includes:

  • FAPI 2.0 profile certification
  • JWT Response from the introspection endpoint (RFC 9701)
  • Diagnostic data
  • Removal of the experimental label from OpenTelemetry metrics
  • Additional license compliance warnings
  • Several bug fixes
  • Numerous small code quality and performance enhancements from the community

Breaking Changes

There are no schema changes needed for IdentityServer 7.3.0. Small code changes maybe be required for some users to upgrade.

  • The SendLogoutNotificationAsync method has been removed from the DefaultBackChannelLogoutService class
  • Client Secret is now required for Clients with ClientCredentials Grant

The SendLogoutNotificationAsync method has been removed from the DefaultBackChannelLogoutService class

  • Fix Concurrent DbContext Access on Back Channel Logout by @​bhazen in Fix Concurrent DbContext Access on Back Channel Logout DuendeSoftware/products#2019
    To fix a bug where when using EntityFramework, code which previously executed in parallel needed to be modified to execute sequentially. This necessitated the removal of the SendLogoutNotificationAsync method in the DefaultBackChannelLogoutService class. Anyone who had previously overridden the SendLogoutNotificationAsync as an extensibility point will likely need to move their customization to the PostLogoutJwt method.

Client Secret is now required for Clients with ClientCredentials Grant

  • Ensure Client Secret is Required for Clients with ClientCredentials Grant by @​bhazen in Ensure Client Secret is Required for Clients with ClientCredentials Grant DuendeSoftware/products#1796
    Previously, it was possible to configure a Client to allow the ClientCredentials Grant without requiring a client secret which is undesirable. The default validation of Clients has been updated to ensure any Client which allows the ClientCredentials grant also sets the RequireClientSecret flag to true to disallow the configuration of a private client to behave like a public client.

Enhancements

FAPI 2.0 Profile Certification

IdentityServer is 7.3.0 is officially certified as conformant with the FAPI 2.0 Security Profile.

JWT Response from Introspection Endpoint

IdentityServer now supports RFC 9701 to return a JWT Response from the Introspection endpoint.

Diagnostic Data

Diagnostic data has been added to IdentityServer to help support with troubleshooting. Read more about this new feature in our docs. TODO: link to docs

7.2.5

This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 7.2.x users upgrade.

GHSA-mxv6-xwqj-ww2p

What's changed

  • PAR: Pushed authorization requests are now rejected when the request's client_id does not exactly match the authenticated client, as required by RFC 9126. Custom IPushedAuthorizationRequestValidator implementations remain responsible for enforcing this binding.
  • PAR: Implicit-only clients can no longer use AllowUnregisteredPushedRedirectUris. These clients do not authenticate at the PAR endpoint, so they must register their redirect URIs.
  • PAR: When 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.

Upgrade notes

  • Implicit-only clients that relied on unregistered pushed redirect URIs must register those redirect URIs.
  • Unregistered non-https PAR redirect URIs (for example http://localhost during local development) must be registered or moved to https.

Full Changelog: DuendeSoftware/products@is-7.2.4...is-7.2.5

7.2.4

This is a patch release that fixes a null reference exception that could occur if a client configuration is removed while active server side sessions exist that involve that client.

Detailed changelog

Full Changelog: DuendeSoftware/products@is-7.2.3...is-7.2.4

7.2.3

This is a patch release that fixes a regression where multiple WWW-authenticate headers where issued.

What's Changed

Full Changelog: DuendeSoftware/products@is-7.2.2...is-7.2.3

7.2.2

This is a patch release that

  • Hardens the default configuration of the sensitive values filters and
  • Fixes mTLS binding so that port numbers can be used as part of mTLS domain

Sensitive Values Filter Defaults

hardens the security of the default configuration that controls the redaction in logs of parameters passed to the Pushed Authorization (PAR) and Authorize endpoint, ensuring that client secrets and client assertions are not logged by default.

In particular, the default value of AuthorizeRequestSensitiveValuesFilter and PushedAuthorizationSensitiveValuesFilter have been changed to both be ["client_secret", "client_assertion", "id_token_hint"].

PAR requests sometimes are handled by the same code path as authorize requests, so this makes both filters the same by default.

mTLS port number

The MtlsOptions.DomainName can now include a port number.

Detailed Changelog

Full Changelog: DuendeSoftware/products@is-7.2.1...is-7.2.2

7.2.1

This is a patch release of IdentityServer that fixes a bug where a private_key_jwt client authentication token would be rejected if it had no typ header, even if strict validation of such tokens was not enabled.

What's Changed

7.2.0

IdentityServer 7.2 is a significant release that includes:

  • Optional strict validation of private_key_jwt audiences, implementing RFC 7523 bis
  • Optional caching of the discovery endpoint
  • Less log noise when issuing the use_dpop_nonce response from the token endpoint
  • Bug fixes and optimizations

Upgrading

There are no breaking changes or schema updates required to upgrade from IdentityServer 7.1 to 7.2.

Upgrading from IdentityServer 7.2.0-preview.1

We have moved the StrictClientAssertionAudienceValidation option that was introduced in 7.2.0-preview.1 into a new Preview section of the options. This new section provides a mechanism for us to deliver new features more quickly, and gives us the flexibility to change implementation details, behavior, or the API surface. Users can opt in to preview features at their own discretion, with the understanding that we make a stronger commitment to API stability once a feature leaves preview. Our intent with Preview flags is to be able to iterate quickly while still providing stability.

We've decided to mark StrictClientAssertionAudienceValidation as a preview option since the formal specification that it is based on (RFC 7523 bis) has not yet been adopted by the IETF OAuth working group.

RFC 7523 bis

RFC 7523 bis is a proposed update to RFC 7523 in which two new requirements for private_key_jwt client assertions are proposed:

  • That the audience (aud claim) must be the issuer of the authorization server and must be a single string
  • That the type (typ header) must be "client-authentication+jwt"

Similar strict audience validation requirements can be found in the FAPI 2.0 Profile.

The intent of the audience validation is to prevent certain academic attacks against OAuth ecosystems that include multiple Authorization Servers in which one of the Authorization Servers is compromised or malicious. The new type header value provides a mechanism to facilitate upgrades, because conforming clients that adopt the proposed changes will produce a token that can be easily distinguished by looking for the new type.

IdentityServer 7.2 includes preview support for RFC 7523 bis. Client applications can opt in to this support by setting the new type header; assertions that set the typ header to client-authentication+jwt always have their audience validated strictly. Other clients can continue to authenticate with private_key_jwts as they do today. IdentityServer can be configured to force clients to update by setting the option options.Preview.StrictClientAssertionAudienceValidation. When that flag is enabled, all private_key_jwt client assertions must set the typ to client-authentication+jwt, and must set their audience to the IdentityServer's issuer.

Discovery Document Caching

We've heard reports of cases where a high volume of requests to the discovery endpoint caused memory pressure and strain on server resources. This could happen in a solution with many clients calling the discovery endpoint, such as native (mobile) clients, SPA clients, or microservices that connect directly to the identity provider. It could also happen if misconfigured clients fail to cache the discovery response.

We’ve added a preview feature that allows you to cache the endpoint output using your distributed cache registration, with the default cache being an in-memory implementation. The cache is meant to reduce pressure when a sudden spike in requests occurs.

You must set the following property in your IdentityServerOptions instance to enable discovery document caching:

#pragma warning disable DUENDEPREVIEW001
pipeline.Options.Preview.EnableDiscoveryDocumentCache = true;
#pragma warning restore DUENDEPREVIEW001
pipeline.Options.Preview.DiscoveryDocumentCacheDuration = TimeSpan.FromMinutes(1);

It's best to keep the cache time low if you utilize the CustomEntries element on the discovery document or implement a custom IDiscoveryResponseGenerator.
This feature is a step in optimizing Duende IdentityServer to utilize server resources and improve performance. More benchmarking and tuning will follow.

use_dpop_nonce Log Noise Reduction

One way to configure DPoP is to require a server-issued nonce value. A nonce prevents replay or pre-generation of the proof tokens used in DPoP by having the authorization server provide a nonce value that the client must include in its signatures. That nonce is provided to the client through a protocol error response.

In IdentityServer 7.1 and earlier, this raised the TokenIssuedFailureEvent because, technically, the token endpoint returns an error. However, this interaction is an expected part of the interaction between client and server. It isn’t an error in the usual sense of the word, and it can happen quite often, resulting in lots of noise in the logs. Therefore, we no longer raise the TokenIssuedFailureEvent when returning a server-generated DPoP nonce.

For those still interested in knowing these errors are occurring, we have added additional Debug log messages to help diagnose and troubleshoot your client implementations. Because these messages are low severity, you must explicitly enable them in your environments to see them. The existing OTel metrics that track token error responses are unchanged, as they don’t add noise to the logs.

Detailed changelog

... (truncated)

7.2.0-preview.1

This is the first preview of IdentityServer 7.2. Highlights include:

  • Optional strict validation of private_key_jwt audiences
  • Error events are no longer raised for the use_dpop_nonce response from the token endpoint
  • Bug fixes and optimizations

Upgrading

There are no breaking changes or schema updates required to upgrade from IdentityServer 7.1 to 7.2.

What's Changed

New Contributors

Full Changelog: DuendeSoftware/products@is-7.1.0...is-7.2.0-preview.1

7.1.3

This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 7.1.x users upgrade.

GHSA-mxv6-xwqj-ww2p

What's changed

  • PAR: Pushed authorization requests are now rejected when the request's client_id does not exactly match the authenticated client, as required by RFC 9126. Custom IPushedAuthorizationRequestValidator implementations remain responsible for enforcing this binding.
  • PAR: Implicit-only clients can no longer use AllowUnregisteredPushedRedirectUris. These clients do not authenticate at the PAR endpoint, so they must register their redirect URIs.
  • PAR: When 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.

Upgrade notes

  • Implicit-only clients that relied on unregistered pushed redirect URIs must register those redirect URIs.
  • Unregistered non-https PAR redirect URIs (for example http://localhost during local development) must be registered or moved to https.

Full Changelog: DuendeSoftware/products@is-7.1.1...is-7.1.3

7.1.1

This is a patch release that fixes a bug that could cause sessions to expire instead of sliding.

What's Changed

7.0.10

This is a security patch release of IdentityServer that hardens validation of pushed authorization requests (PAR). We recommend all 7.0.x users upgrade.

GHSA-mxv6-xwqj-ww2p

What's changed

  • PAR: Pushed authorization requests are now rejected when the request's client_id does not exactly match the authenticated client, as required by RFC 9126. Custom IPushedAuthorizationRequestValidator implementations remain responsible for enforcing this binding.
  • PAR: Implicit-only clients can no longer use AllowUnregisteredPushedRedirectUris. These clients do not authenticate at the PAR endpoint, so they must register their redirect URIs.
  • PAR: When 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.

Upgrade notes

  • Implicit-only clients that relied on unregistered pushed redirect URIs must register those redirect URIs.
  • Unregistered non-https PAR redirect URIs (for example http://localhost during local development) must be registered or moved to https.

Full Changelog: DuendeSoftware/products@f28cac9...is-7.0.10

Commits viewable in compare view.

Updated FluentValidation.AspNetCore from 11.3.0 to 11.3.1.

Release notes

Sourced from FluentValidation.AspNetCore's releases.

11.3.1

Release notes

Please read the upgrade guide if you are moving from 10.x to 11.x

Changes in 11.3.1

  • Compatibility with FluentValidation 12.x

Changes in 11.3.0

Changes in 11.2.2

  • Fix issue where implicit child validation could still be executed for Record types even when disabled (#​7)
  • Add additional overload of AddToModelState that doesn't require a prefix (#​5)

Changes in 11.2.1

Changes in 11.2.0

  • The dependency on the core FluentValidation library now uses a floating version.

Changes in 11.1.3

Changes in 11.1.2

  • Fixed NullReferenceException being thrown in AddFluentValidationClientsideAdapters caused by a missing registration for IValidatorFactory

Changes in 11.1.1

Changes in 11.1.0

Changes in 11.0

  • Throw exceptions when async validator is invoked synchronously (#​1705)
  • Remove deprecated RunDefaultMvcValidationAfterFluentValidationExecutes option from ASP.NET integration.

Downloads

Binaries can be downloaded from nuget:

Commits viewable in compare view.

Updated MailKit from 4.18.1 to 4.18.2.

Release notes

Sourced from MailKit's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated MassTransit from 8.2.5 to 8.5.12.

Release notes

Sourced from MassTransit's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated MassTransit.RabbitMQ from 8.2.5 to 8.5.12.

Release notes

Sourced from MassTransit.RabbitMQ's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.AspNetCore.Authentication.JwtBearer from 8.0.31 to 8.0.34.

Release notes

Sourced from Microsoft.AspNetCore.Authentication.JwtBearer's releases.

8.0.34

Release

What's Changed

Full Changelog: dotnet/aspnetcore@v8.0.32...v8.0.34

8.0.33

Release

Full Changelog: dotnet/aspnetcore@v8.0.32...v8.0.33

8.0.32

Release

What's Changed

Full Changelog: dotnet/aspnetcore@v8.0.31...v8.0.32

Commits viewable in compare view.

Updated Microsoft.AspNetCore.Identity.EntityFrameworkCore from 8.0.31 to 8.0.34.

Release notes

Sourced from Microsoft.AspNetCore.Identity.EntityFrameworkCore's releases.

8.0.34

Release

What's Changed

Full Changelog: dotnet/aspnetcore@v8.0.32...v8.0.34

8.0.33

Release

Full Changelog: dotnet/aspnetcore@v8.0.32...v8.0.33

8.0.32

Release

What's Changed

  • [release/8.0] Update branding to 8.0.32 by @​vseanreesermsft in...

Description has been truncated

Bumps dotnet-ef from 8.0.31 to 8.0.34
Bumps dotnet-reportgenerator-globaltool from 5.5.11 to 5.6.0
Bumps Duende.IdentityServer.AspNetIdentity from 7.0.0 to 7.4.14
Bumps FluentValidation.AspNetCore from 11.3.0 to 11.3.1
Bumps MailKit from 4.18.1 to 4.18.2
Bumps MassTransit from 8.2.5 to 8.5.12
Bumps MassTransit.RabbitMQ from 8.2.5 to 8.5.12
Bumps Microsoft.AspNetCore.Authentication.JwtBearer from 8.0.31 to 8.0.34
Bumps Microsoft.AspNetCore.Identity.EntityFrameworkCore from 8.0.31 to 8.0.34
Bumps Microsoft.AspNetCore.Mvc.Testing from 8.0.31 to 8.0.34
Bumps Microsoft.EntityFrameworkCore.SqlServer from 8.0.31 to 8.0.34
Bumps Microsoft.EntityFrameworkCore.Tools from 8.0.31 to 8.0.34
Bumps Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore from 8.0.31 to 8.0.34
Bumps Microsoft.NET.Test.Sdk from 18.10.1 to 18.12.0
Bumps Microsoft.VisualStudio.Azure.Containers.Tools.Targets from 1.21.0 to 1.23.0
Bumps MimeKit from 4.18.1 to 4.18.2
Bumps QRCoder from 1.4.3 to 1.8.1
Bumps QuestPDF from 2024.3.0 to 2024.12.3
Bumps Swashbuckle.AspNetCore from 6.5.0 to 6.9.0

---
updated-dependencies:
- dependency-name: dotnet-ef
  dependency-version: 8.0.34
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: other
- dependency-name: dotnet-reportgenerator-globaltool
  dependency-version: 5.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: other
- dependency-name: Duende.IdentityServer.AspNetIdentity
  dependency-version: 7.4.14
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: other
- dependency-name: FluentValidation.AspNetCore
  dependency-version: 11.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: other
- dependency-name: MailKit
  dependency-version: 4.18.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: other
- dependency-name: MailKit
  dependency-version: 4.18.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: other
- dependency-name: MimeKit
  dependency-version: 4.18.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: other
- dependency-name: MassTransit
  dependency-version: 8.5.12
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: other
- dependency-name: MassTransit.RabbitMQ
  dependency-version: 8.5.12
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: other
- dependency-name: MassTransit.RabbitMQ
  dependency-version: 8.5.12
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: other
- dependency-name: Microsoft.AspNetCore.Authentication.JwtBearer
  dependency-version: 8.0.34
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: other
- dependency-name: Microsoft.AspNetCore.Identity.EntityFrameworkCore
  dependency-version: 8.0.34
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: other
- dependency-name: Microsoft.AspNetCore.Mvc.Testing
  dependency-version: 8.0.34
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: other
- dependency-name: Microsoft.EntityFrameworkCore.SqlServer
  dependency-version: 8.0.34
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: other
- dependency-name: Microsoft.EntityFrameworkCore.Tools
  dependency-version: 8.0.34
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: other
- dependency-name: Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore
  dependency-version: 8.0.34
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: other
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-version: 18.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: other
- dependency-name: Microsoft.VisualStudio.Azure.Containers.Tools.Targets
  dependency-version: 1.23.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: other
- dependency-name: QRCoder
  dependency-version: 1.8.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: other
- dependency-name: QuestPDF
  dependency-version: 2024.12.3
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: other
- dependency-name: Swashbuckle.AspNetCore
  dependency-version: 6.9.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: other
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Nov 14, 2026
@cheZA99 cheZA99 closed this Nov 14, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 14, 2026

Copy link
Copy Markdown
Contributor Author

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

@dependabot
dependabot Bot deleted the dependabot/nuget/dot-config/other-4b53f3f4f2 branch November 14, 2026 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant