15 years ago
WSSec processed messages are always pretty printed
I am using SoapUI pro 3.5.1 on Windows, but also tried a fix with the open version 3.5.1.
As part of our WS-Security testing we use signed and encrypted responses and enjoy the Security processing of SoapUI.
The issue we're encountering is that the response from our service (which was encrypted, but the same holds for signing or both) is processed and then pretty printed even if pretty printing is disabled in the SoapUI interface.
This is a problem for us because our payload itself is a WS-Trust RSTR which includes a signed SAML security token, and pretty printing the payload invalidates it. Not processing the response leaves it encrypted but unusable.
Looking into the code, I see that the
method of the WsdlSinglePartHttpResponse class contains a line (~52)
The logic to determine the pretty behavior should be linked to the user option for pretty printing, not mandatory with WS-Sec processing.
Thanks Eviware, we love using your tools.
/Jon
As part of our WS-Security testing we use signed and encrypted responses and enjoy the Security processing of SoapUI.
The issue we're encountering is that the response from our service (which was encrypted, but the same holds for signing or both) is processed and then pretty printed even if pretty printing is disabled in the SoapUI interface.
This is a problem for us because our payload itself is a WS-Trust RSTR which includes a signed SAML security token, and pretty printing the payload invalidates it. Not processing the response leaves it encrypted but unusable.
Looking into the code, I see that the
private void processIncomingWss( WsdlRequest wsdlRequest, PropertyExpansionContext context )
method of the WsdlSinglePartHttpResponse class contains a line (~52)
XmlUtils.serializePretty( document, writer );I rebuilt the open version of soapUI 3.5.1 with
XmlUtils.serialize( document, writer );instead and I am then able to successfully use the whitespace sensitive encrypted payload.
The logic to determine the pretty behavior should be linked to the user option for pretty printing, not mandatory with WS-Sec processing.
Thanks Eviware, we love using your tools.
/Jon