SharedJwkCache
Caches JWKS values for all clients created in the same environment. This is especially useful for shared-memory execution environments such as Vercel's Fluid Compute, AWS Lambda or Supabase's Edge Functions. Regardless of how many clients are created, if they share the same storage key they will use the same JWKS cache, significantly speeding up Auth.getClaims with asymmetric JWTs.
Functions
Link copied to clipboard
Returns the current JwkCacheEntry, or null if no cache entry was found
Link copied to clipboard
Updates the current cache entry with entry