Comparing version 3.1.0 to 3.2.0
@@ -9,3 +9,3 @@ const path = require('path'); | ||
const DEFAULT_ALGORITHM_SIGN = 'secp521r1'; // 'prime256v1'; | ||
const ALLOWED_ALGORITHMS = ['HS256', 'HS384', 'HS512', 'RS256', 'RS384', 'RS512', 'PS256', 'PS384', 'PS512', 'ES256', 'ES384', 'ES512']; | ||
const ALLOWED_ALGORITHMS = ['HS256', 'HS384', 'HS512', 'RS256', 'RS384', 'RS512', 'PS256', 'PS384', 'PS512', 'ES256', 'ES384', 'ES512', 'none']; | ||
@@ -12,0 +12,0 @@ const TOKEN_COOKIE_REGEXP = /access_token\s*=([^;]+?)(?:;|$)/; |
{ | ||
"name": "kitten-jwt", | ||
"version": "3.1.0", | ||
"version": "3.2.0", | ||
"description": "Keep It Simple, Stupid, Secure and Fast JWT module", | ||
@@ -5,0 +5,0 @@ "main": "index.js", |
@@ -107,2 +107,4 @@ # Kitten JWT | ||
**Note**: The 'none' algorithm allows unsigned JWTs. While the JWT specification allows this algorithm (see RFC 7519), it introduces security risks and should be used with caution. | ||
- payload | ||
@@ -209,4 +211,8 @@ | ||
## CHANGELOG | ||
## CHANGELOG* | ||
**3.2.0** | ||
- Add support for the 'none' algorithm (JWT without signature) | ||
**3.1.0** | ||
@@ -213,0 +219,0 @@ |
36004
266