-
Notifications
You must be signed in to change notification settings - Fork 475
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"invalid signature" after updating passport saml #456
Comments
Update xml-crypto back to 1.4.0 resolve the issue |
Was a corresponding bug filed with |
@cjbarth There are newer releases of xml-crypto out. Could test an upgrade with them? 1.5.3 or 2.0.0. The 2.0.0 release addresses some security concerns but is a breaking change. |
@yj188 Could you please provide a reproduction for the error you encountered? Ideally, it would be nice to have a test added that would pass with v1.4.0 and fail with v1.5.3. |
passport saml version: 1.3.4 --> 1.3.5 Error: Invalid signature |
@Harsha3878 , are you saying that v1.3.4 works, but v1.3.5 fails with the current test suite? |
@cjbarth No i tried both the version but it failed with both intial version i was using was 0.15.0 |
I'm closing this now due to updating the |
passport saml version: 1.1.0 --> 1.3.5
xml-crypto: 1.4.0 --> 1.5.3
xml-encryption: 0.11.2 ->1.2.1
Error: Invalid signature
at /var/task/node_modules/passport-saml/lib/passport-saml/saml.js:611:15
at _fulfilled (/var/task/node_modules/q/q.js:854:54)
at /var/task/node_modules/q/q.js:883:30
at Promise.promise.promiseDispatch (/var/task/node_modules/q/q.js:816:13)
at /var/task/node_modules/q/q.js:624:44
at runSingle (/var/task/node_modules/q/q.js:137:13)
at flush (/var/task/node_modules/q/q.js:125:13)
at processTicksAndRejections (internal/process/task_queues.js:79:11)
The text was updated successfully, but these errors were encountered: