Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
2.25.4
-
None
-
Unknown
-
Description
Currently, the content of the provider's discovery setup is cached forever (at least until next restart or authenticator extension reload).
While it's very rare for this content to change, it would still be better to refresh it from time to time. It could then also be reused to store other things, like the JWs (see OIDC-317).
Attachments
Issue Links
- relates to
-
OIDC-317 Cache the JWKSet used to verify signatures
-
- Open
-