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
This is happening because 'node-forge' used to accept a "single line" certificate in private_key = pki.privateKeyFromPem(options.key) (check commit 7aaa734). But now, after this commit, crypto module is in use:
Error: error:0909006C:PEM routines:get_name:no start line
at Object.privateDecrypt (node:internal/crypto/cipher:79:12)
at decryptKeyInfoWithScheme (/root/inbound-saml-0.17.0/node_modules/xml-encryption/lib/xmlenc.js:258:26)
at decryptKeyInfo (/root/inbound-saml-0.17.0/node_modules/xml-encryption/lib/xmlenc.js:246:14)
at Object.decrypt (/root/inbound-saml-0.17.0/node_modules/xml-encryption/lib/xmlenc.js:187:24)
Environment
Please provide the following:
Version of this library used: 2.0.0
Adicional Context
Even if that depends on a lib (node-forge/crypto), this change caused downstream modules to BREAK, so from a design perspective it's still an UNDOCUMENTED BREAKING CHANGE, even that it may also be treated as a bug to (hot)fix.
The text was updated successfully, but these errors were encountered:
Description
After upgrading to version 2.0.0,
decrypt
throws when using single line private key. (without pvk header/footer and without line breaks). As reported in node-saml/passport-saml#672 and GluuFederation/inbound-saml#154 .This is happening because 'node-forge' used to accept a "single line" certificate in
private_key = pki.privateKeyFromPem(options.key)
(check commit 7aaa734). But now, after this commit,crypto
module is in use:node-xml-encryption/lib/xmlenc.js
Line 258 in e8df80c
Reproduction
output:
Environment
Adicional Context
Even if that depends on a lib (node-forge/crypto), this change caused downstream modules to BREAK, so from a design perspective it's still an UNDOCUMENTED BREAKING CHANGE, even that it may also be treated as a bug to (hot)fix.
The text was updated successfully, but these errors were encountered: