Specify clientRegistrationId in TokenRelay filter #2922
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR adds the ability to specify a
clientRegistrationIdfor theTokenRelayGatewayFilter.clientRegistrationIdis specified, it is used to build theOAuth2AuthorizeRequest.oauth2Login(), the existingOAuth2AuthenticationToken.getAuthorizedClientRegistrationId()is used.With this enhancement, the gateway can be used to manage many
ClientRegistrations, and each route can determine which client registration to use. This is incredibly useful in scenarios where there are (for example):a) multiple authorization servers in use simultaneously
b) multiple client authentication methods in use simultaneously
c) some/all downstream services require a distinct
clientId,audclaim, etc.d) some/all downstream services require different token formats (e.g. JWT, opaque)