Closed gijsboer closed 1 year ago
I have the same issue using SOOCirle as my IDP. When I check the request with https://www.samltool.com/validate_response.php is says it is valid
should have updated this ticket, but after I enabled SAML encryption in passport-saml, I could correctly validate it. And using the tool xmlsec, I was able to see the actual canonicalized XML, digest, and everything else that I needed to see what the difference was (there is, the canonicalized XML is different).
Thanks for the response! Do you know how enabling SAML encryption in passport-saml effected the implementation of xml-crypto? I'm just using xml-crypto. Were there additional transforms or options?
If I remember correctly, <sometag></sometag>
would get translated as <sometag/>
or the other way around. Xmlsec1 produces the right XML, so you can compare the output of xml-crypto against that and will show you the reason why it fails.
It appears that this issue is resolved, so I'll close it. If I'm mistaken, please reply to reopen.
Hello,
I'm trying to use the signature validation option, but I can't get it to validate the signature unfortunately. I've tried using samlify and passport-saml, both are using xml-crypto and both give the same answer.
Certificate used to validate it:
Idp Entity ID:
https://ssodev.huberto.org/FIM/sps/HUBDVSAML20/saml20
Service provider EntityId:GatewayWAMService
SP Attribute consume Service endpoint:https://ssodev.huberto.org/FIM/sps/HUBDVSAML20/saml20
Target URL:http://localhost:3000/login/callback
SAML response received/to be validated:
The error that I get is in
validationErrors
:I half-assume that the canonicalized XML is wrong, but I can't determine what the canonicalized XML is that is being used on the IDP, since it's not in my control.
Does anyone know what the problem could be?
Let me know if more info is needed!