Bump Duende.IdentityServer from 7.2.3 to 7.3.2#5
Closed
dependabot[bot] wants to merge 1 commit intomainfrom
Closed
Bump Duende.IdentityServer from 7.2.3 to 7.3.2#5dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
--- updated-dependencies: - dependency-name: Duende.IdentityServer dependency-version: 7.3.2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
.NET
Author
|
Superseded by #9. |
dependabot
bot
deleted the
dependabot/nuget/Duende.IdentityServer-7.3.2
branch
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.2.3 to 7.3.2.
Release notes
Sourced from Duende.IdentityServer's releases.
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.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
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)