-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: auth0/node-jsonwebtoken
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v4.2.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: auth0/node-jsonwebtoken
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v5.0.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 10 commits
- 6 files changed
- 2 contributors
Commits on Apr 6, 2015
-
Configuration menu - View commit details
-
Copy full SHA for a77df6d - Browse repository at this point
Copy the full SHA a77df6dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 24a3700 - Browse repository at this point
Copy the full SHA 24a3700View commit details -
Configuration menu - View commit details
-
Copy full SHA for 954bd7a - Browse repository at this point
Copy the full SHA 954bd7aView commit details
Commits on Apr 7, 2015
-
Configuration menu - View commit details
-
Copy full SHA for 35036b1 - Browse repository at this point
Copy the full SHA 35036b1View commit details
Commits on Apr 10, 2015
-
As `jws@3.0.0` changed the verify method signature to be `jws.verify(signature, algorithm, secretOrKey)`, the token header must be decoded first in order to make sure that the `alg` field matches one of the allowed `options.algorithms`. After that, the now validated `header.alg` is passed to `jws.verify` As the order of steps has changed, the error that was thrown when the JWT was invalid is no longer the `jws` one: { [Error: Invalid token: no header in signature 'a.b.c'] code: 'MISSING_HEADER', signature: 'a.b.c' } That old error (removed from jws) has been replaced by a `JsonWebTokenError` with message `invalid token`. That's why this change will bump be a major.
Configuration menu - View commit details
-
Copy full SHA for 1e46234 - Browse repository at this point
Copy the full SHA 1e46234View commit details -
Configuration menu - View commit details
-
Copy full SHA for 19e6cc6 - Browse repository at this point
Copy the full SHA 19e6cc6View commit details -
Renaming
header.alg
mismatch exception toinvalid algorithm
and a……dding more mismatch tests.
Configuration menu - View commit details
-
Copy full SHA for 9f24ffd - Browse repository at this point
Copy the full SHA 9f24ffdView commit details -
Merge pull request #78 from auth0/update-to-jws-3
Update to jws@^3.0.0
Configuration menu - View commit details
-
Copy full SHA for 634b8ed - Browse repository at this point
Copy the full SHA 634b8edView commit details -
Merge pull request #75 from auth0/dschenkelman-patch-1
Only set iat if there is none
Configuration menu - View commit details
-
Copy full SHA for e900282 - Browse repository at this point
Copy the full SHA e900282View commit details -
Configuration menu - View commit details
-
Copy full SHA for db8fb93 - Browse repository at this point
Copy the full SHA db8fb93View commit details
There are no files selected for viewing