Add support for nested user-name-attribute using dot notation #16857
+217
−5
Conversation
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
spring-projects-issues
added
the
status: waiting-for-triage
Implement the ability to use dot notation in user-name-attribute to access nested properties in OAuth2 user info responses. Closes spring-projectsgh-16390 Signed-off-by: yybmion <yunyubin54@gmail.com>
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.
Closes gh-16390
Hi team, this PR adds support for nested properties in the OAuth2 user-name-attribute using dot notation.
For example, if a provider returns a nested response like
{"data": {"username": "user1"}},users can now directly configure
user-name-attribute: data.usernamewithout writing custom code.Implementation
Testing
Added tests for
All tests pass and existing functionality is preserved.