mirror of
https://github.com/hanzoai/node-jsonwebtoken.git
synced 2026-09-24 17:00:48 +00:00
Alberto Pose
1e46234201
As `[email protected]` 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.
33 lines
622 B
JSON
33 lines
622 B
JSON
{
|
|
"name": "jsonwebtoken",
|
|
"version": "4.2.2",
|
|
"description": "JSON Web Token implementation (symmetric and asymmetric)",
|
|
"main": "index.js",
|
|
"scripts": {
|
|
"test": "mocha"
|
|
},
|
|
"repository": {
|
|
"type": "git",
|
|
"url": "https://github.com/auth0/node-jsonwebtoken"
|
|
},
|
|
"keywords": [
|
|
"jwt"
|
|
],
|
|
"author": "auth0",
|
|
"license": "MIT",
|
|
"bugs": {
|
|
"url": "https://github.com/auth0/node-jsonwebtoken/issues"
|
|
},
|
|
"dependencies": {
|
|
"jws": "^3.0.0"
|
|
},
|
|
"devDependencies": {
|
|
"atob": "^1.1.2",
|
|
"chai": "^1.10.0",
|
|
"mocha": "^2.1.0"
|
|
},
|
|
"engines": {
|
|
"npm": ">=1.4.28"
|
|
}
|
|
}
|