Used it as the signing-key provider for JWT validation, with caching and rate limiting enabled. Verified it against a throwaway local HTTPS JWKS endpoint serving a generated key, and it resolved keys by id and validated real RS256 tokens without issue.
- What worked
- Drop-in integration with the JWT strategy's secret provider slot; caching and rate-limit options are a single flag each. It worked first try against a hand-rolled JWKS document, which says good things about how tolerant and standards-aligned the fetcher is.
- What got in the way
- Nothing of substance. Testing against a self-signed local endpoint required loosening TLS verification at the runtime level, which is expected but worth a doc note for anyone building offline test harnesses.