-
Notifications
You must be signed in to change notification settings - Fork 6.1k
Add option to use jwksCache in NimbusJwtDecoder #7639
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -244,6 +244,12 @@ public void jwsAlgorithmWhenNullThenThrowsException() { | |
Assertions.assertThatCode(() -> builder.jwsAlgorithm(null)).isInstanceOf(IllegalArgumentException.class); | ||
} | ||
|
||
@Test | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please also add a unit test that confirms that the provided cache gets used. |
||
public void jwkSetCacheWhenNullThenThrowsException() { | ||
NimbusJwtDecoder.JwkSetUriJwtDecoderBuilder builder = withJwkSetUri(JWK_SET_URI); | ||
Assertions.assertThatCode(() -> builder.jwkSetCache(null)).isInstanceOf(IllegalArgumentException.class); | ||
} | ||
|
||
@Test | ||
public void restOperationsWhenNullThenThrowsException() { | ||
NimbusJwtDecoder.JwkSetUriJwtDecoderBuilder builder = withJwkSetUri(JWK_SET_URI); | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer exposing an interface that is more powerful than the
JWKSetCache
interface. If an application really wants to supply aJWKSetCache
, then it's quite simple to construct aDefaultJWTProcessor
directly and pass that to theNimbusJwtDecoder
constructor.What if this took a
org.springframework.cache.Cache
instead? Then this builder could internally wrap that in aCacheJWKSetCache
implementation, similar to the design ofRestOperationsResourceRetreiver
.The nice thing about doing that is that an application can then use whatever caching mechanism they wish, be it Caffeine, Hazelcast, or something else.
Another nice this is that using
Cache
allows the entries to be key-value based which is better suited for a multi-tenant resource server that is caching keys from multiple issuers.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jzheaux Sry, but how should it help to multi-tenant resource server? I mean in multi-tenant environment we will have a separate
AuthenticationManager
for each tenant, that means for each tenant we will have: uniquejwks-uri
-> uniquedecoder
-> so uniquejwkSetCache
, I don't see possible way for multiple keys to be stored inJWKSetCache
with the current implementationThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question, @20fps. I guess it comes down to what parts of your infra are multi-tenant. If your cache is multi-tenant, then each
AuthenticationManager
could have aJwtDecoder
that shares the same cache - each JWK Set keyed, for example, by that tenant's JWK Set Uri.If each tenant has its own cache, then that point is moot. My main point is that by introducing a key to the cache grants additional flexibility - multi-tenancy is one way that flexibility could be leveraged.