Skip to content

Latest commit

 

History

History
447 lines (264 loc) · 36.8 KB

CHANGELOG.md

File metadata and controls

447 lines (264 loc) · 36.8 KB
Raw

Change Log

All notable changes to this project will be documented in this file starting from version v4.0.0. This project adheres to Semantic Versioning.

8.4.0 - 2018-11-14

New Functionality

Bug Fixes

Docs

Test Improvements

CI

8.3.0 - 2018-06-11

8.2.2 - 2018-05-30

8.2.1 - 2018-04-05

8.2.0 - 2018-03-02

8.1.1 - 2018-01-22

8.1.0 - 2017-10-09

8.0.1 - 2017-09-12

8.0.0 - 2017-09-06

Breaking changes: See Migration notes from v7

7.4.3 - 2017-08-17

  • Fix breaking change on 7.4.2 for empty secret + "none" algorithm (sync code style) (PR 386)

7.4.2 - 2017-08-04

7.4.1 - 2017-05-17

7.4.0 - 2017-04-24

7.3.0 - 2017-02-13

7.2.1 - 2016-12-07

7.2.0 - 2016-12-06

7.1.10 - 2016-12-06

7.1.9 - 2016-08-11

7.1.8 - 2016-08-10

7.1.7 - 2016-07-29

7.1.6 - 2016-07-15

7.1.5 - 2016-07-15

7.1.4 - 2016-07-14

7.1.2 - 2016-07-12

7.1.1 - 2016-07-12

7.1.0 - 2016-07-12

7.0.0 - 2016-05-19

6.2.0 - 2016-04-29

6.1.2 - 2016-04-29

6.1.0 - 2016-04-27

6.0.1 - 2016-04-27

This was an immediate change after publishing 6.0.0.

6.0.0 - 2016-04-27

5.7.0 - 2016-02-16

5.6.1 - 2016-02-16

5.6.0 - 2016-02-16

5.5.4 - 2016-01-04

5.5.3 - 2016-01-04

5.5.2 - 2016-01-04

5.5.1 - 2016-01-04

5.5.0 - 2015-12-28

5.4.0 - 2015-10-02

5.3.0 - 2015-10-02

5.1.0 - 2015-10-02

5.0.5 - 2015-08-19

5.0.3 - 2015-07-15

5.0.2 - 2015-06-15

5.0.1 - 2015-05-15

[5.0.0] - 2015-04-11

Changed

  • [sign] Only set defautl iat if the user does not specify that argument.

https://github.com/auth0/node-jsonwebtoken/commit/e900282a8d2dff1d4dec815f7e6aa7782e867d91 https://github.com/auth0/node-jsonwebtoken/commit/35036b188b4ee6b42df553bbb93bc8a6b19eae9d https://github.com/auth0/node-jsonwebtoken/commit/954bd7a312934f03036b6bb6f00edd41f29e54d9 https://github.com/auth0/node-jsonwebtoken/commit/24a370080e0b75f11d4717cd2b11b2949d95fc2e https://github.com/auth0/node-jsonwebtoken/commit/a77df6d49d4ec688dfd0a1cc723586bffe753516

Security

  • [verify] Update to jws@^3.0.0 and renaming header.alg mismatch exception to invalid algorithm and adding more mismatch tests.

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.

Important: versions >= 4.2.2 this library are safe to use but we decided to deprecate everything < 5.0.0 to prevent security warnings from library node-jws when doing npm install.

https://github.com/auth0/node-jsonwebtoken/commit/634b8ed0ff5267dc25da5c808634208af109824e https://github.com/auth0/node-jsonwebtoken/commit/9f24ffd5791febb449d4d03ff58d7807da9b9b7e https://github.com/auth0/node-jsonwebtoken/commit/19e6cc6a1f2fd90356f89b074223b9665f2aa8a2 https://github.com/auth0/node-jsonwebtoken/commit/1e4623420159c6410616f02a44ed240f176287a9 https://github.com/auth0/node-jsonwebtoken/commit/954bd7a312934f03036b6bb6f00edd41f29e54d9 https://github.com/auth0/node-jsonwebtoken/commit/24a370080e0b75f11d4717cd2b11b2949d95fc2e https://github.com/auth0/node-jsonwebtoken/commit/a77df6d49d4ec688dfd0a1cc723586bffe753516

[4.2.2] - 2015-03-26

Fixed

[4.2.1] - 2015-03-17

Fixed

[4.2.0] - 2015-03-16

Security

  • [asymmetric-keys] Making sure a token signed with an asymmetric key will be verified using a asymmetric key. When the verification part was expecting a token digitally signed with an asymmetric key (RS/ES family) of algorithms an attacker could send a token signed with a symmetric algorithm (HS* family).

The issue was caused because the same signature was used to verify both type of tokens (verify method parameter: secretOrPublicKey).

This change adds a new parameter to the verify called algorithms. This can be used to specify a list of supported algorithms, but the default value depends on the secret used: if the secretOrPublicKey contains the string BEGIN CERTIFICATE the default is [ 'RS256','RS384','RS512','ES256','ES384','ES512' ] otherwise is [ 'HS256','HS384','HS512' ]. (jfromaniello) https://github.com/auth0/node-jsonwebtoken/commit/c2bf7b2cd7e8daf66298c2d168a008690bc4bdd3 https://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687

[4.1.0] - 2015-03-10

Changed

  • Assume the payload is JSON even when there is no typ property. 5290db1

[4.0.0] - 2015-03-06

Changed

  • The default encoding is now utf8 instead of binary. 92d33bd
  • Add encoding as a new option to sign. 1fc385e
  • Add ignoreExpiration to verify. 8d4da27
  • Add expiresInSeconds to sign. dd156cc

Fixed

  • Fix wrong error message when the audience doesn't match. 44e3c8d
  • Fix wrong error message when the issuer doesn't match. 44e3c8d
  • Fix wrong iat and exp values when signing with noTimestamp. 331b7bc