Since public JWKs shouldn't change once they are set, it should be acceptable to cache the response and then revalidate the cache when an unknown key is encountered. With the recent canvas degradation, being able to cache these would save some really long response times I'm seeing.
Since public JWKs shouldn't change once they are set, it should be acceptable to cache the response and then revalidate the cache when an unknown key is encountered. With the recent canvas degradation, being able to cache these would save some really long response times I'm seeing.