ATO-1424: Support filtering keys by use in JwkCache #5887
Merged
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.
Wider context of change
Previously, we added a JwkCache that would cache JWKs from a URL. This class did not differentiate between key uses though, so could retrieve a signing key to be used in encryption for example.
What’s changed
A
keyUse
field has been added toJwkCacheEntry
. When keys are retrieved from the JWKS URL, they are filtered to only include keys that match the use field. Additionally,JwkCache
has been renamed toEncryptionJwkCache
to be more specific.Checklist