Closed RoSk0 closed 3 years ago
I think it's an easy fix if we flip these two parts of the code; https://github.com/simplesamlphp/saml2/blob/master/src/SAML2/SOAPClient.php#L158-L165 i.e. first parse the message (your case with non-soap response should fail there) and then see if the SOAP-response contains a Fault.
@RoSk0 is this something you can test for us?
Hi @tvdijen ,
Thanks for suggestion. I implemented this fix and tested it - now I see only one log entry for the bad( non soap ) response and SimpleSAMLphp show the user user error screen which is great.
Take a look at a PR please, it's not exactly as you suggested but I think close enough.
If it works, I'm not complaining ;) Thanks a lot @RoSk0 for your work! I'll tag 4.2.0 and make sure this change finds it's way upstream
Thanks!
While testing new certificates I encountered that if I receive this response:
from Artifact binding endpoint it passes
and
and goes into
producing white screen for the end user and this in the logs:
There should be smarts to detect this in either getSOAPFault() or send() method itself.