chore(deps): bump github.com/lestrrat-go/jwx/v2 from 2.0.18 to 2.1.2

[dependabot]

Bumps github.com/lestrrat-go/jwx/v2 from 2.0.18 to 2.1.2.

Release notes

Sourced from github.com/lestrrat-go/jwx/v2's releases.

v2.1.2

What's Changed

• Bump golang.org/x/crypto from 0.25.0 to 0.26.0 by @​dependabot in lestrrat-go/jwx#1168
• Fix document of how to parse PEM via CLI by @​kg0r0 in lestrrat-go/jwx#1174
• Wrap the errors from functions called within ParseRequest by @​lestrrat in lestrrat-go/jwx#1176
• V2 modernize workflows by @​lestrrat in lestrrat-go/jwx#1182
• Dependabot fixes for v2 by @​lestrrat in lestrrat-go/jwx#1183
• Use variable by @​lestrrat in lestrrat-go/jwx#1186
• Bump golang.org/x/crypto from 0.26.0 to 0.27.0 by @​dependabot in lestrrat-go/jwx#1177
• Bump golangci/golangci-lint-action from 6.1.0 to 6.1.1 by @​dependabot in lestrrat-go/jwx#1199
• Bump golang.org/x/crypto from 0.27.0 to 0.28.0 by @​dependabot in lestrrat-go/jwx#1208
• update comments to include iat by @​cscochris in lestrrat-go/jwx#1216

New Contributors

• @​kg0r0 made their first contribution in lestrrat-go/jwx#1174
• @​cscochris made their first contribution in lestrrat-go/jwx#1216

Full Changelog: lestrrat-go/jwx@v2.1.1...v2.1.2

v2.1.1

v2.1.1 Jul 28 2024
  * Update minimum required go version to go 1.20
  * Update tests to work on 32-bit systems.
  * [jwa] Add RSA_OAEP_384 and RSA_OAEP_512
  * [jwa] `jwa.SignatureAlgorithm` now has a `IsSymmetric` method.
  * [jwa] Add `jwa.RegisterSignatureAlgorithmOptions()` to register new algorithms while
    specifying extra options. Currently only `jwa.WithSymmetricAlgorithm()` is supported.
  * [jws] Clearly mark `jws.WithHeaders()` as deprecated

v2.1.0

v2.1.0 18 Jun 2024
[New Features]
  * [jwt] Added `jwt.ParseCookie()` function
  * [jwt] `jwt.ParseRequest()` can now accept a new option, jwt.WithCookieKey() to
    specify a cookie name to extract the token from.
  * [jwt] `jwt.ParseRequest()` and `jwt.ParseCookie()` can accept the `jwt.WithCookie()` option,
    which will, upon successful token parsing, make the functions assign the *http.Cookie
    used to parse the token. This allows users to further inspect the cookie where the
    token came from, should the need arise.
  * [jwt] (BREAKING CHANGE) `jwt.ParseRequest()` no longer automatically looks for "Authorization" header when
    only `jwt.WithFormKey()` is used. This behavior is the same for `jwt.WithCookieKey()` and
    any similar options that may be implemented in the future.
  # previously
  jwt.ParseRequest(req) // looks under Authorization
  jwt.ParseReuqest(req, jwt.WithFormKey("foo")) // looks under foo AND Authorization
  jwt.ParseReuqest(req, jwt.WithHeaderKey("Authorization"), jwt.WithFormKey("foo")) // looks under foo AND Authorization

</tr></table>

... (truncated)

Changelog

Sourced from github.com/lestrrat-go/jwx/v2's changelog.

v2.1.2 25 Oct 2024

• [jwt] jwt.ParseRequest now uses %w to embed errors returned from jwt.ParseHeader, jwt.ParseCookie, and jwt.ParseForm, allowing users to correctly call errors.Is(err, jwt.ErrTokenExpired) and the like. Previously the error returned from jwt.ParseRequest showed in human readable format what the problem was, but it was not programmatically possible to determine the error type using errors.Is (#1175)

v2.1.1 Jul 28 2024

• Update minimum required go version to go 1.20
• Update tests to work on 32-bit systems.
• [jwa] Add RSA_OAEP_384 and RSA_OAEP_512
• [jwa] jwa.SignatureAlgorithm now has a IsSymmetric method.
• [jwa] Add jwa.RegisterSignatureAlgorithmOptions() to register new algorithms while specifying extra options. Currently only jwa.WithSymmetricAlgorithm() is supported.
• [jws] Clearly mark jws.WithHeaders() as deprecated

v2.1.0 18 Jun 2024 [New Features]

• [jwt] Added jwt.ParseCookie() function

• [jwt] jwt.ParseRequest() can now accept a new option, jwt.WithCookieKey() to specify a cookie name to extract the token from.

• [jwt] jwt.ParseRequest() and jwt.ParseCookie() can accept the jwt.WithCookie() option, which will, upon successful token parsing, make the functions assign the *http.Cookie used to parse the token. This allows users to further inspect the cookie where the token came from, should the need arise.

• [jwt] (BREAKING CHANGE) jwt.ParseRequest() no longer automatically looks for "Authorization" header when only jwt.WithFormKey() is used. This behavior is the same for jwt.WithCookieKey() and v2.0.22 UNRELEASED [New Features]

• [jwt] Added jwt.ParseCookie() function

• [jwt] jwt.ParseRequest() can now accept a new option, jwt.WithCookieKey() to specify a cookie name to extract the token from.

• [jwt] jwt.ParseRequest() and jwt.ParseCookie can accept the jwt.WithCookie() option, which will, upon successful token parsing, make the functions assign the *http.Cookie used to parse the token. This allows users to further inspect the cookie where the token came from, should the need arise.

• [jwt] jwt.ParseRequest() no longer automatically looks for "Authorization" header when only jwt.WithFormKey() is used. This behavior is the same for jwt.WithCookieKey() and any similar options that may be implemented in the future.

  previously

  jwt.ParseRequest(req) // looks under Authorization jwt.ParseReuqest(req, jwt.WithFormKey("foo")) // looks under foo AND Authorization jwt.ParseReuqest(req, jwt.WithHeaderKey("Authorization"), jwt.WithFormKey("foo")) // looks under foo AND Authorization

  since this release

  jwt.ParseRequest(req) // same as before jwt.ParseRequest(req, jwt.WithFormKey("foo")) // looks under foo jwt.ParseRequest(req, jwt.WithHeaderKey("Authorization"), jwt.WithFormKey("foo")) // looks under foo AND Authorization

... (truncated)

Commits

• 536b643 Merge branch 'develop/v2' into v2
• 4f04913 Update Changes
• 42ae987 update comments to include iat (#1216)
• 42920f4 Bump golang.org/x/crypto from 0.27.0 to 0.28.0 (#1208)
• 5728179 Bump golangci/golangci-lint-action from 6.1.0 to 6.1.1 (#1199)
• 9e26e23 Bump golang.org/x/crypto from 0.26.0 to 0.27.0 (#1177)
• f573d26 Use variable (#1186)
• 4aae462 Dependabot fixes for v2 (#1183)
• c5d7db2 V2 modernize workflows (#1182)
• 551d76f Wrap the errors from functions called within ParseRequest (#1176)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)