jwt
jwt copied to clipboard
Community maintained clone of https://github.com/dgrijalva/jwt-go
Type conversion, key will not allocate memory
this cleans up the code a bit and avoids unnecessary memory allocations
* Add new functions for creating SigningMethod structs, like `NewSigningMethodECDSA`. * Use `var` instead of `init` functions. * Let RegisterSigningMethod take a `SigningMethod` type, and let `RegisterSigningMethodFunc` take an algorithm...
It would be great to have a bit of documentation on how to sign a token using private/public pair keys. I've found an example here : http://www.inanzzz.com/index.php/post/kdl9/creating-and-validating-a-jwt-rsa-token-in-golang
Migrated from https://github.com/dgrijalva/jwt-go/issues/249: > dgrijalva commented on Mar 8, 2018 > > How far down the rabbit hole should we go with this? See the issue thread for more details
#119 The code comment for jwt.ParsePublicKeyFromPEM stated that it could parse PKCS1 public keys. However, it couldn't. I created a unit test that generates a public PKCS1 key and the...
The code comment for rsa_utils.go says it's for a PKCS1 or PKCS8 public key (`ParseRSAPublicKeyFromPEM parses a PEM encoded PKCS1 or PKCS8 public key ParseRSAPublicKeyFromPEM parses a PEM encoded PKCS1...
The package has a policy of not depending on third party packages and consuming only the standard library but for well structured tests we could benefit from using a more...
Migrated from https://github.com/dgrijalva/jwt-go/issues/375: > Filet-de-S commented on Jan 18, 2020 • > > It's inconvenient to check it with strcmp instead of switch err.(type) > > *jwt.ValidationError is the same...
This isn't done as the tests haven't been verified but this moves errors to go 1.13. I can finish it but I don't want to burn a lot of time...