fix(deps): update module github.com/micahparks/jwkset to v0.5.17 #2415
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.3.1
->v0.5.17
Release Notes
MicahParks/jwkset (github.com/MicahParks/jwkset)
v0.5.17
Compare Source
v0.5.16
Compare Source
v0.5.15
: Less strict validationCompare Source
The purpose of this release is to use less strict validation for JWK. This will allow users to work with non-RFC compliant JWK Sets for small padding mistakes.
Two padding related reasons for this are:
For padding specifically, this project is only comparing integers after they are parsed from Base64 raw URL encoding by default. To turn on strict validation, there will be a new field on jwkset.ValidateOptions named StrictPadding.
An example for
1
would be a bug in this project were mandatory leading padding was absent: https://github.com/MicahParks/jwkset/issues/18An example for
2
would be a Firebase service that was reported to be incompatible with this project: https://github.com/MicahParks/jwkset/issues/23Relevant issues:
Relevant pull requests:
v0.5.14
Compare Source
v0.5.13
Compare Source
The purpose of this release is to correctly pad EC JWK parameters with leading zeros where required by RFC 7518.
For
"x"
and"y"
:For
"d"
:This is to bring the project into RFC compliance with RFC 7518 Section 6.2.1.2, 6.2.1.3, and 6.2.2.1.
Relevant issues:
What's Changed
Full Changelog: MicahParks/jwkset@v0.5.12...v0.5.13
v0.5.12
Compare Source
v0.5.11
Compare Source
v0.5.10
Compare Source
v0.5.9
: jwksetinfer tool multi-PEM bugCompare Source
A bug in the
cmd/jwksetinfer
tool caused multiple PEM file inputs to only output the final PEM key as a JWK Set. This is because the metadata wasn't being passed in and the all key IDs were the same empty string.Thank you @aarnaud for discovering the bug and fixing it!
Relevant pull requests:
v0.5.8
Compare Source
v0.5.7
Compare Source
v0.5.6
: Refresh on unknown key IDCompare Source
The purpose of this release is to change the default HTTP client to add a feature that refreshes remote JWK Set resources when trying to read a key ID kid that has not been found in the local cache.
This requires rate limiting and the
pkg.go.dev/golang.org/x/time/rate
has been added as a dependency for that.Related pull requests:
v0.5.5
: Consistent optional behavior for X.509 certificate thumbprintsCompare Source
This release fixes a bug where X.509 certificate thumbprints were not optional when a
JWKMarshal
without these fields was used inNewJWKFromMarshal
.Thank you, @joshkaplinsky, for reporting this bug!
Relevant pull requests:
Relevant issues:
v0.5.4
Compare Source
v0.5.3
Compare Source
v0.5.2
Compare Source
v0.5.1
Compare Source
v0.5.0
: Add HTTP ClientCompare Source
This release contains a Golang HTTP client for JWK Sets.
v0.4.0
: Add website and X.509 supportCompare Source
This project now supports all standardized JSON Web Key parameters, including X.509 assets that I could find. Please open an issue if you find some that are not supported.
Additionally, I made a website for this project. The website is mostly for generating and inspecting JSON Web Keys. Check it out at https://jwkset.com
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.