Fix OIDC discovery to fallback on text/html responses #17927
+72
−0
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.
Summary
Some providers return
200
withtext/html
for/.well-known/openid-configuration
. Previously, discovery stopped at thefirst endpoint. This PR makes discovery continue to the next candidate so it can fall back to the OAuth 2.0 Authorization Server metadata endpoint.
Motivation
What Changed
oauth2/oauth2-client
ClientRegistrations#getBuilder
: recordUnknownContentTypeException
and try the next discovery endpoint
issuerWhenOidcHtmlThenFallbackToOAuth2ThenSuccess
issuerWhenFirstEndpoint5xxThenThrowsIllegalArgumentException
Behavior
succeeds via OAuth 2.0 AS metadata when available.
Closes gh-17036