Repository navigation
Bump the other group with 19 updates - #11
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
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>
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
Bot
deleted the
dependabot/nuget/dot-config/other-4b53f3f4f2
branch
November 14, 2026 16:35
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 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:
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:
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.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.7.3.2
This is a patch release that optimizes key creation when not using X509 Certificates.
Details
7.3.1
This is a patch release that fixes a bug and enables a System.Text.Json serialization option.
Details
7.3.0
IdentityServer 7.3.0 is a significant release that includes:
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
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
SendLogoutNotificationAsyncmethod in theDefaultBackChannelLogoutServiceclass. Anyone who had previously overridden theSendLogoutNotificationAsyncas an extensibility point will likely need to move their customization to thePostLogoutJwtmethod.Client Secret is now required for Clients with ClientCredentials Grant
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
RequireClientSecretflag 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
... (truncated)
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:
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
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
SendLogoutNotificationAsyncmethod in theDefaultBackChannelLogoutServiceclass. Anyone who had previously overridden theSendLogoutNotificationAsyncas an extensibility point will likely need to move their customization to thePostLogoutJwtmethod.Client Secret is now required for Clients with ClientCredentials Grant
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
RequireClientSecretflag 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
... (truncated)
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
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.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
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
AuthorizeRequestSensitiveValuesFilterandPushedAuthorizationSensitiveValuesFilterhave 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.DomainNamecan 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_jwtclient authentication token would be rejected if it had notypheader, 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:
private_key_jwtaudiences, implementing RFC 7523 bisuse_dpop_nonceresponse from the token endpointUpgrading
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
StrictClientAssertionAudienceValidationoption 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
StrictClientAssertionAudienceValidationas 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_jwtclient assertions are proposed:audclaim) must be the issuer of the authorization server and must be a single stringtypheader) 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
typheader toclient-authentication+jwtalways have their audience validated strictly. Other clients can continue to authenticate withprivate_key_jwts as they do today. IdentityServer can be configured to force clients to update by setting the optionoptions.Preview.StrictClientAssertionAudienceValidation. When that flag is enabled, allprivate_key_jwtclient assertions must set thetyptoclient-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
IdentityServerOptionsinstance to enable discovery document caching:It's best to keep the cache time low if you utilize the
CustomEntrieselement on the discovery document or implement a customIDiscoveryResponseGenerator.This feature is a step in optimizing Duende IdentityServer to utilize server resources and improve performance. More benchmarking and tuning will follow.
use_dpop_nonceLog Noise ReductionOne 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
TokenIssuedFailureEventbecause, 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 theTokenIssuedFailureEventwhen 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:
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
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.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
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@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
Changes in 11.3.0
Filterproperty to auto-validation configuration to optionally include/exclude certain types from auto-validation (Could AddFluentValidationAutoValidation() take a filter parameter so we can opt in/out of automatic validtion? FluentValidation/FluentValidation#2091)Changes in 11.2.2
AddToModelStatethat doesn't require a prefix (#5)Changes in 11.2.1
AddFluentValidation(see Announcement: Deprecation ofRegisterValidator...methods within calls toAddFluentValidationFluentValidation/FluentValidation#1963)Changes in 11.2.0
Changes in 11.1.3
AddFluentValidationregistration methods. These have been replaced withAddFluentValidationAutoValidationandAddFluentValidationClientsideAdapters(see Announcement: Changes to ASP.NET Integration registration methods (AddFluentValidation()) FluentValidation/FluentValidation#1965)Changes in 11.1.2
NullReferenceExceptionbeing thrown inAddFluentValidationClientsideAdapterscaused by a missing registration forIValidatorFactoryChanges in 11.1.1
NullReferenceExceptionbeing thrown inAddFluentValidationClientsideAdapters(FluentValidation.AspNetCore is throwing during bootstrap FluentValidation/FluentValidation#1969)Changes in 11.1.0
ToDictionarymethod toValidationResult(particularly useful when working with Minimal APIs)-services.AddFluentValidationAutoValidation()andservices.AddFluentValidationClientsideAdapters()as replacements forservices.AddFluentValidation()(Announcement: Changes to ASP.NET Integration registration methods (AddFluentValidation()) FluentValidation/FluentValidation#1965)Changes in 11.0
RunDefaultMvcValidationAfterFluentValidationExecutesoption 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
36ba75ftobc548fdby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest from36ba75ftobc548fddotnet/aspnetcore#69625365965ftobe938cdby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/MessagePack-CSharp from365965ftobe938cddotnet/aspnetcore#69538bc548fdtob66cffcby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest frombc548fdtob66cffcdotnet/aspnetcore#69811Full 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
3940de9to36ba75fby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest from3940de9to36ba75fdotnet/aspnetcore#68922Full 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
36ba75ftobc548fdby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest from36ba75ftobc548fddotnet/aspnetcore#69625365965ftobe938cdby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/MessagePack-CSharp from365965ftobe938cddotnet/aspnetcore#69538bc548fdtob66cffcby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest frombc548fdtob66cffcdotnet/aspnetcore#69811Full 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
Description has been truncated