-
Notifications
You must be signed in to change notification settings - Fork 79
Description
Recently, I have encountered a couple of SAML implementations where the service provider does not accept the output generated by SAMLRaider. I have tested this by making a change in the SAML Raider edit box, undoing that change, and submitting the request, which is rejected by the server. Resubmitting the original code works fine.
Closer inspection shows that this is caused by linebreaks that are inserted by SAMLRaider. It seems the first couple of linebreaks are accepted by the server, but in my case inserting a linebreak (manually, without using SAMLRaider) between ds:SignedInfo and <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> triggers an error at the server. This might well be a bug in the SAML implementation rather than in SAMLRaider, but nevertheless something that prevents testing with SAMLRaider.
One implementation that seems to suffer from this is Saml2-js.
Would it be possible to find a solution for this? If it is not possible to find the root cause, would it be possible to add a setting that disables adding the linebreaks?