Resource Server - Multi-Tenant Jwt Decoder by Issuer #6779
Closed
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
gburboz
commented
Apr 15, 2019
| jwk-set-uri: ${mockwebserver.url}/.well-known/jwks.json | ||
| multi-tenant-jwt: |
There was a problem hiding this comment.
I did not have mock server that supports JWTs with iss claims hence have put these as sample. They need not necessarily support JWT access tokens with iss claim in it.
gburboz
commented
Apr 15, 2019
| return jwtDecoder.decode(token); | ||
| } | ||
|
|
||
| private String parseAndFindIssuer(String token) { |
There was a problem hiding this comment.
Unfortunately this parsing occurs twice, once here and also when NimbusJwtDecoder is invoked
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.
Resolves issue #6778 : Resource Server - Multi-Tenant Jwt Decoder by Issuer