You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a good approach for APIs that throttle requests and could end up returning 429's to JWK fetches, when multiple workers run concurrently.
At the moment, the hacky workaround is to override the jwk_set_cache client attribute right after instantiating it, replacing it with a Redis client that implements the Protocol you suggested.
Great project!
I'm using it with my Django project, where it runs multiple containers with scaling. I have a redis server shared between these instances.
I would like to cache JWKs in redis.
I could provide a PR if people are interested.
I'd propose the following:
The text was updated successfully, but these errors were encountered: