jwt icon indicating copy to clipboard operation
jwt copied to clipboard

Community maintained clone of https://github.com/dgrijalva/jwt-go

Results 98 jwt issues
Sort by recently updated
recently updated
newest added

## Is ParseWithClaims function make a memory leak ? I use `golang-jwt/jwt/[email protected]` to parse jwt string to struct by ParseWithClaims. Our service have `1350 req/sec` at peak time. So I...

## The Problem Right now the [following code executes without error](https://go.dev/play/p/9WqOc6k3UlQ): ```go func main() { bogusKey := []byte("") token := jwt.NewWithClaims(jwt.SigningMethodHS256, jwt.MapClaims{ "foo": "bar", "nbf": time.Date(2015, 10, 10, 12, 0,...

In certain scenarios it's nice to perform the validation of a token separate parsing it. For example when checking client assertions in OAuth 2.0 flows so that the authorization server...

My scenario is, that for example I want skip the validation under certain circumstances. To achieve that, I invoke `jwt.ParseWithClaims(...)` and want to check afterward whether it was the signature...

The note in the docs (I guess sourced from the [comment here](https://github.com/golang-jwt/jwt/blob/v5.2.1/parser.go#L225)) > Parse parses, validates, verifies the signature and returns the parsed token. keyFunc will receive the parsed token...

as discussed here: https://github.com/golang-jwt/jwt/issues/392

Removes the global `MarshalSingleStringAsArray` and makes it configurable per token. This allows safely using both configuration options within the same application. This is a breaking change so is intended mostly...

next

the `crypto.PublicKey` is defined as any, although I don't know why it compiles. But the type checking does throw an exception ![image](https://github.com/user-attachments/assets/c689ce00-44ff-44b2-8c5a-74a8ab243ed3) ```go // VerificationKey represents a public or secret...

We can currently change the precision of timestamps getting serialized by modifying `TimePrecision` [here](https://github.com/golang-jwt/jwt/blob/main/types.go#L18). However we are running into an issue where we have to serialize/validate different jwt tokens of...