HttpsJwks and HttpsJwksVerificationKeyResolver with Pluggable Cache implementation

[Todd Fredrich]

In microservice and multi-tenant SaaS scenarios the retrieval of customer JWKS endpoints can result in large numbers of keys being retrieved and cached across clusters of services which increases the need for external, shared caching along with potentially many HttpsJwks instances.

It would be great to have a version of HttpsJwks that offers a pluggable cache implementation along with a version of HttpsJwksVerificationKeyResolver which can cache (and resolve over) multiple HttpsJwks instances for this use case.

Or… perhaps it’s already possible and I’m just missing how to do it correctly. In this case some documentation around this use case would be helpful.

Thanks!

[Brian Campbell]

Putting this one "on hold" for now based on our conversation.