Fix OAuth2 documentation: Correct OAuth2ClientHttpRequestInterceptor usage #16172
Conversation
This file contains 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
spring-projects-issues
added
the
status: waiting-for-triage
harpreets789
force-pushed
the
gh-16165
branch
from
a7127d1 to
95b8bb8
Compare
|
The sample code in the documentation has been corrected by instantiating the Fixing the previous incorrect constructor usage in both the Java and Kotlin code samples. |
sjohnr
added
in: docs
|
Thanks @harpreets789, this is now merged into |
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.
The code example in the "Access Protected Resources for the Current User" -> "Configure RestClient with ClientHttpRequestInterceptor" section was incorrect. Updated the example to use the correct
OAuth2ClientHttpRequestInterceptorconstructor and added a call tosetClientRegistrationIdResolver. This ensures accurate usage of the API.Closes gh-16165.