Release v5.2.1

Release v5.2.0

Release v5.1.0

enable jwt.ParsePublicKeyFromPEM to parse PKCS1 Public Key (#120)

Adjusting the error checking example (#270)

This PR adjusts the error checking example so that a check for an invalid signature is also included.

See discussion in #143

`v5` Pre-Release (#234)

Co-authored-by: Micah Parks <[email protected]>
Co-authored-by: Michael Fridman <[email protected]>

Allow strict base64 decoding (#259)

By default base64 decoder works in non-strict mode which
allows tweaking signatures having padding without failing validation.

This creates a potential problem if application treats token value as an identifier.

For example ES256 signature has length of 64 bytes and two padding symbols (stripped by default).
Therefore its base64-encoded value can only end with A, Q, g and w.
In non-strict mode last symbol could be tweaked resulting in 16 distinct
token values having the same signature and passing validation.

This change adds backward-compatible global config variable DecodeStrict
(similar to existing DecodePaddingAllowed) that enables strict base64 decoder mode.

See also golang/go#15656.

Signed-off-by: Alexander Yastrebov <[email protected]>

No pointer embedding in the example (#255)

Fixes #223

chore: remove unused claims in RSA table driven test (#212)

Revert "feat: port clockskew support (#139)" (#184)

This reverts commit d489c99.