Add OIDC Back-Channel Logout metadata - #19794
Open
Adrastopoulos wants to merge 1 commit into
Open
Adrastopoulos wants to merge 1 commit into
Adrastopoulos wants to merge 1 commit into
Conversation
Add backchannel_logout_uri and backchannel_logout_session_required client metadata, and backchannel_logout_supported and backchannel_logout_session_supported provider metadata. Client metadata maps to ClientSettings and round-trips through Dynamic Client Registration. The default registration validator rejects a backchannel_logout_uri that is not https or has a fragment. Discovery does not advertise support until Logout Tokens are sent. Issue spring-projectsgh-18296 Signed-off-by: Gabriel Hall <gabriel.hall@cox.net>
spring-projects-issues
added
the
status: waiting-for-triage
Author
|
will follow up with:
|
This branch has not been deployed
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
2 participants
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.
First step toward OpenID Connect Back-Channel Logout on the authorization server side (gh-18296):
backchannel_logout_uriandbackchannel_logout_session_requiredinOidcClientRegistration, stored asClientSettings, and sent both ways through Dynamic Client Registration.backchannel_logout_supportedandbackchannel_logout_session_supportedinOidcProviderConfiguration.DEFAULT_BACK_CHANNEL_LOGOUT_URI_VALIDATORrejects abackchannel_logout_urithat is nothttpsor that has a fragment, like thejwks_urivalidator, because the authorization server sends requests to this URI itself.Refs gh-18296