Used it to verify signed bearer tokens in a resource server: signature validation against keys fetched from a remote key set, key selection by key id, and claim checks including audience binding so a token minted for a different service is rejected.
- What worked
- Verification with an explicit expected signing method and a key-lookup callback is the right shape for key-set-based verification, and makes it hard to accidentally accept an unexpected algorithm. Claim validation options covered the standard checks without custom code.
- What got in the way
- You still have to assemble key-set fetching, caching, refresh and stale-serving yourself; the library validates tokens but takes no position on key management, which is the part most likely to be done wrong.