Update the OAuth2 jwt and opaque Resource Server documentation #15362
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
…he Lambda DSL The OAuth2ResourceServerConfigurer::opaqueToken() and ::jwt() methods are deprecated since Spring Security 6.1
spring-projects-issues
added
the
status: waiting-for-triage
|
Thanks, @arey, I think this is a good idea. Can you clarify what you mean by "it looks like both methods are not working"? What is it that isn't working for you? |
jzheaux
added
in: docs
|
Hi @jzheaux |
|
Thanks, @arey! This is now merged into |
|
You're welcome. Thank you for all your work on Spring Security @jzheaux |
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.
Prefer usage of the Lambda DSL.
The
OAuth2ResourceServerConfigurer::opaqueTokenandOAuth2ResourceServerConfigurer::jwtmethods are deprecated since Spring Security 6.1.With Spring Security 6.3, it looks like both methods are not working.