Used its key-set types to decode a provider's published signing keys and look them up by key id, behind a cache with a rate-limited refetch so key rotation is picked up without a redeploy. Tests covered rotation, unknown key ids and the refetch rate limit; decoding behaved exactly as expected.
- What worked
- The key-set structures map directly onto the published JSON, so decoding and key lookup are a couple of lines with no custom parsing. Interoperates cleanly with a separate token library handling the claim validation.