Verification of RS256-encoded JWT does not work with Node 18
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, node.js
- Domain
- authentication, backend, security
Research direction
Start by reproducing the jwt.verify(myJWT, myKey, {algorithms: ["RS256"]}) example with node-jsonwebtoken 8.5.1 under Node 18 and compare it with Node 16. Use the reported OpenSSL decoder error and Keycloak-generated RS256 JWT as the baseline; done means verification works on the affected Node 18 environment without regressing Node 16 behavior.
Written by the indexing model from the issue text.
Description
Please do not report security vulnerabilities here. The Responsible Disclosure Program details the procedure for disclosing security issues.
Thank you in advance for helping us to improve this library! Please read through the template below and answer all relevant questions. Your additional work here is greatly appreciated and will help us respond as quickly as possible. For general support or usage questions, use the Auth0 Community or Auth0 Support. Finally, to avoid duplicates, please search existing Issues before submitting one here.
By submitting an Issue to this repository, you agree to the terms within the Auth0 Code of Conduct.
Description
Provide a clear and concise description of the issue, including what you expected to happen.
I'm trying to verify a JWT created by Keycloak. It uses the RS256 algorithm. That works with Node 16, but not with Node 18. I get the following error:
error:1E08010C:DECODER routines::unsupported
This is probably due to the version bump of OpenSSL in Node (Node 16 uses openssl: '1.1.1q+quic' while 18 shows openssl: '3.0.5+quic'.
See here: https://github.com/openssl/openssl/issues/17378 Apparently, it's a feature not a bug...
Reproduction
console.log(jwt.verify(myJWT, myKey, {algorithms: ["RS256"]}));
Environment
Please provide the following:
- Version of this library used: 8.5.1
- Version of the platform or framework used, if applicable: -
- Other relevant versions (language, server software, OS, browser): Node 16 / 10, Windows 10
- Other modules/plugins/libraries that might be involved: OpenSSL included in Node
- Dominant language
- JavaScript
- Stars
- 18.2k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from auth0/node-jsonwebtoken
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
auth0/node-jsonwebtoken#1042 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
auth0/node-jsonwebtoken#1000 · 2 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 65/100
auth0/node-jsonwebtoken#1046 ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
auth0/node-jsonwebtoken#1034 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
auth0/node-jsonwebtoken#1032 ·
All issues in auth0/node-jsonwebtoken
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
antfu-collective/icones#398 ·
-
ECmail.com Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
wesbos/burner-email-providers#554 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
radiantearth/stac-browser#1023 ·
-
HMR stops working Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
components-web-app/docs#92 ·