-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update all dependencies (main) #237
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: redhat-renovate-bot <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@redhat-renovate-bot: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Syntactically incorrect PR. /hold |
This PR contains the following updates:
v4.5.1
->v5.2.1
v2.21.0
->v2.22.2
v1.35.1
->v1.36.2
v0.30.3
->v0.32.0
v0.31.2
->v0.32.0
v0.30.3
->v0.32.0
v0.30.3
->v0.32.0
f0e62f9
->2c72e55
18e509b
->24370be
v1.3.1
->v1.4.0
v1.3.1
->v1.4.0
v0.0.0
->v0.7.0
Release Notes
golang-jwt/jwt (github.com/golang-jwt/jwt/v4)
v5.2.1
Compare Source
What's Changed
New Contributors
Full Changelog: golang-jwt/jwt@v5.2.0...v5.2.1
v5.2.0
Compare Source
What's Changed
NewValidator
by @oxisto in https://github.com/golang-jwt/jwt/pull/349New Contributors
Full Changelog: golang-jwt/jwt@v5.1.0...v5.2.0
v5.1.0
Compare Source
What's Changed
ErrInvalidType
instead ofjson.UnsupportedTypeError
by @oxisto in https://github.com/golang-jwt/jwt/pull/316New Contributors
Full Changelog: golang-jwt/jwt@v5.0.0...v5.1.0
v5.0.0
Compare Source
🚀 New Major Version
v5
🚀It's finally here, the release you have been waiting for! We don't take breaking changes lightly, but the changes outlined below were necessary to address some of the challenges of the previous API. A big thanks for @mfridman for all the reviews, all contributors for their commits and of course @dgrijalva for the original code. I hope we kept some of the spirit of your original
v4
branch alive in the approach we have taken here.~@oxisto, on behalf of @golang-jwt/maintainers
Version
v5
contains a major rework of core functionalities in thejwt-go
library. This includes support for several validation options as well as a re-design of theClaims
interface. Lastly, we reworked how errors work under the hood, which should provide a better overall developer experience.Starting from v5.0.0, the import path will be:
For most users, changing the import path should suffice. However, since we intentionally changed and cleaned some of the public API, existing programs might need to be updated. The following sections describe significant changes and corresponding updates for existing programs.
Parsing and Validation Options
Under the hood, a new
validator
struct takes care of validating the claims. A long awaited feature has been the option to fine-tune the validation of tokens. This is now possible with severalParserOption
functions that can be appended to mostParse
functions, such asParseWithClaims
. The most important options and changes are:WithLeeway
to support specifying the leeway that is allowed when validating time-based claims, such asexp
ornbf
.iat
claim. Usage of this claim is OPTIONAL according to the JWT RFC. The claim itself is also purely informational according to the RFC, so a strict validation failure is not recommended. If you want to check for sensible values in these claims, please use theWithIssuedAt
parser option.WithAudience
,WithSubject
andWithIssuer
to support checking for expectedaud
,sub
andiss
.WithStrictDecoding
andWithPaddingAllowed
options to allow previously global settings to enable base64 strict encoding and the parsing of base64 strings with padding. The latter is strictly speaking against the standard, but unfortunately some of the major identity providers issue some of these incorrect tokens. Both options are disabled by default.Changes to the
Claims
interfaceComplete Restructuring
Previously, the claims interface was satisfied with an implementation of a
Valid() error
function. This had several issues:Since all the validation functionality is now extracted into the validator, all
VerifyXXX
andValid
functions have been removed from theClaims
interface. Instead, the interface now represents a list of getters to retrieve values with a specific meaning. This allows us to completely decouple the validation logic with the underlying storage representation of the claim, which could be a struct, a map or even something stored in a database.Supported Claim Types and Removal of
StandardClaims
The two standard claim types supported by this library,
MapClaims
andRegisteredClaims
both implement the necessary functions of this interface. The oldStandardClaims
struct, which has already been deprecated inv4
is now removed.Users using custom claims, in most cases, will not experience any changes in the behavior as long as they embedded
RegisteredClaims
. If they created a new claim type from scratch, they now need to implemented the proper getter functions.Migrating Application Specific Logic of the old
Valid
Previously, users could override the
Valid
method in a custom claim, for example to extend the validation with application-specific claims. However, this was always very dangerous, since once could easily disable the standard validation and signature checking.In order to avoid that, while still supporting the use-case, a new
ClaimsValidator
interface has been introduced. This interface consists of theValidate() error
function. If the validator sees, that aClaims
struct implements this interface, the errors returned to theValidate
function will be appended to the regular standard validation. It is not possible to disable the standard validation anymore (even only by accident).Usage examples can be found in example_test.go, to build claims structs like the following.
Changes to the
Token
andParser
structThe previously global functions
DecodeSegment
andEncodeSegment
were moved to theParser
andToken
struct respectively. This will allow us in the future to configure the behavior of these two based on options supplied on the parser or the token (creation). This also removes two previously global variables and moves them to parser optionsWithStrictDecoding
andWithPaddingAllowed
.In order to do that, we had to adjust the way signing methods work. Previously they were given a base64 encoded signature in
Verify
and were expected to return a base64 encoded version of the signature inSign
, both as astring
. However, this made it necessary to haveDecodeSegment
andEncodeSegment
global and was a less than perfect design because we were repeating encoding/decoding steps for all signing methods. Now,Sign
andVerify
operate on a decoded signature as a[]byte
, which feels more natural for a cryptographic operation anyway. Lastly,Parse
andSignedString
take care of the final encoding/decoding part.In addition to that, we also changed the
Signature
field onToken
from astring
to[]byte
and this is also now populated with the decoded form. This is also more consistent, because the other parts of the JWT, mainlyHeader
andClaims
were already stored in decoded form inToken
. Only the signature was stored in base64 encoded form, which was redundant with the information in theRaw
field, which contains the complete token as base64.Most (if not all) of these changes should not impact the normal usage of this library. Only users directly accessing the
Signature
field as well as developers of custom signing methods should be affected.What's Changed
StandardClaims
in favor ofRegisteredClaims
by @oxisto in #235v5
Pre-Release by @oxisto in https://github.com/golang-jwt/jwt/pull/234DecodeSegement
toParser
by @oxisto in https://github.com/golang-jwt/jwt/pull/278Verify
&Sign
to detail why string is not an advisable input for key by @dillonstreator in https://github.com/golang-jwt/jwt/pull/249v5
release by @oxisto in https://github.com/golang-jwt/jwt/pull/291New Contributors
Full Changelog: golang-jwt/jwt@v4.5.0...v5.0.0
onsi/ginkgo (github.com/onsi/ginkgo/v2)
v2.22.2
Compare Source
What's Changed
Full Changelog: onsi/ginkgo@v2.22.1...v2.22.2
v2.22.1
Compare Source
2.22.1
Fixes
Fix CSV encoding
aab3da6
]c09df39
]96a80fc
]43dad69
]Maintenance
c88c634
]4df44bf
]v2.22.0
Compare Source
2.22.0
Features
0fcaa08
]This allows serial tests to be filtered using the
label-filter
Maintenance
Various doc fixes
onsi/gomega (github.com/onsi/gomega)
v1.36.2
Compare Source
Maintenance
v1.36.1
Compare Source
1.36.1
Fixes
1c6c112
]4feb9d7
]v1.36.0
Compare Source
1.36.0
Features
4c964c6
]Maintenance
ece6872
]8e924d7
]kubernetes/api (k8s.io/api)
v0.32.0
Compare Source
v0.31.4
Compare Source
v0.31.3
Compare Source
v0.31.2
Compare Source
v0.31.1
Compare Source
v0.31.0
Compare Source
v0.30.8
Compare Source
v0.30.7
Compare Source
v0.30.6
Compare Source
v0.30.5
Compare Source
v0.30.4
Compare Source
kubernetes/apimachinery (k8s.io/apimachinery)
v0.32.0
Compare Source
v0.31.4
Compare Source
v0.31.3
Compare Source
kubernetes/client-go (k8s.io/client-go)
v0.32.0
Compare Source
v0.31.4
Compare Source
v0.31.3
Compare Source
v0.31.2
Compare Source
v0.31.1
Compare Source
v0.31.0
Compare Source
v0.30.8
Compare Source
v0.30.7
Compare Source
v0.30.6
Compare Source
v0.30.5
Compare Source
v0.30.4
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.