error:09091064:PEM routines:PEM_read_bio_ex:bad base64 decode
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, node.js
- Domain
- authentication, security
Research direction
Start at jwt.verify and trace how the supplied publickey reaches Node.js Verify.verify in internal/crypto/sig.js. The reproduction uses placeholder token and key values, so first obtain complete inputs and reproduce with the reported Node.js 14.16.0 environment; done requires a confirmed project-side cause and a regression test or documented resolution.
Written by the indexing model from the issue text.
Description
Description
Token validated ok at jwt.io. Received error with .verify
Error:
code:'ERR_OSSL_PEM_BAD_BASE64_DECODE'
function:'PEM_read_bio_ex'
library:'PEM routines'
reason:'bad base64 decode'
message:'error:09091064:PEM routines:PEM_read_bio_ex:bad base64 decode'
stack:'Error: error:09091064:PEM routines:PEM_read_bio_ex:bad base64 decode\n at Verify.verify (internal/crypto/sig.js:188:24)
Provide a clear and concise description of the issue, including what you expected to happen.
Reproduction
const jwt = require("jsonwebtoken");
var vtoken = "..."; // validated by jwt.io
var key = "..."; // value copied from jwt.io
var publickey = "-----BEGIN CERTIFICATE-----\n" + key + "\n-----END CERTIFICATE-----";
var payload= jwt.verify(vtoken, publickey, { algorithms: ['RS256'] });
- Screenshots
Environment
Please provide the following:
- 8.5.1
- VSC version: 1.63.1 (system setup)
Commit: fe719cd3e5825bf14e14182fddeb88ee8daf044f
Date: 2021-12-14T02:13:54.292Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19044
- 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 ·