Allow to configure clientId as sub in RequestMapping #532
+64
−5
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
kvokacka
changed the title
ybelMekk
approved these changes
Aug 29, 2023
|
LGTM 😄 @kvokacka Thanks for contributing, can you add a line in the README file about this possibility? |
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.
For Client Credentials grant type allow to dynamically use
clientIdassubclaim inRequestMappingTokenCallback.This is default behavior in
DefaultOAuth2TokenCallbackwould be great to be able to configure the same when usingRequestMappingTokenCallback.Idea is to use
${clientId}as value ofsubfield inclaimswhentokenCallbacksare configured.${clientId}will be replaced by actual clientId in the response.