You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I generated x509 format certificates using the ED25519 algorithm with openssl from the instructions here. I've been reliably getting this error when I call importX509 (I tried as far as I can tell every combination of import... and alg):
mikedh@luna:sandbox$ node key_issue.js
(node:599349) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'raw' of undefined
at spkiFromX509 (/home/mikedh/sandbox/node_modules/jose/dist/node/cjs/key/import.js:68:110)
at getSPKI (/home/mikedh/sandbox/node_modules/jose/dist/node/cjs/key/import.js:73:41)
at importX509 (/home/mikedh/sandbox/node_modules/jose/dist/node/cjs/key/import.js:86:18)
at Object.<anonymous> (/home/mikedh/sandbox/key_issue.js:3:13)
I'm not sure if this is me trying to import an incorrect certificate or a bug with importX509. For what it's worth, openssl can read back the certificates and seems happy. The script I used to call openssl to generate the minimal example below and full console output are in this gist.
Hi @mikedh. Thank you for bringing it up. I kinda knew about this but wasn't counting on certificates without a version number to come up. Guess i was wrong. The latest release has this issue fixed.
What happened?
Hi, thanks for the great library!
I generated x509 format certificates using the ED25519 algorithm with
openssl
from the instructions here. I've been reliably getting this error when I callimportX509
(I tried as far as I can tell every combination ofimport...
andalg
):I'm not sure if this is me trying to import an incorrect certificate or a bug with
importX509
. For what it's worth,openssl
can read back the certificates and seems happy. The script I used to call openssl to generate the minimal example below and full console output are in this gist.Version
4.1.4
Runtime
Node.js
Runtime Details
Node v12.21.1
Code to reproduce
The text was updated successfully, but these errors were encountered: