The purpose of this release is to allow package users to specify which signing algorithms in JWT headers are required for which given keys. Keys from a remote JWK Set had their algorithm checked in release 1.5.2. For discussion, please see the related issue.
Thank you to our new contributor, @sean-rn!
Please note the following functions have been deprecated and replaced:
NewGivenCustom-->NewGivenCustomWithOptionsNewGivenECDSA-->NewGivenECDSAWithOptionsNewGivenEdDSA-->NewGivenEdDSAWithOptionsNewGivenHMAC-->NewGivenHMACWithOptionsNewGivenRSA-->NewGivenRSAWithOptions
This is a consequence of not providing options for given keys in the initial implementation.
Related issues:
Related pull requests: