Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Signing Timestamp/Body in the SOAP message yields error

SA-518

Summary



After signing Timestamp and Body of the SOAP message using SOAPUI client, the following error is returned in the SOAP response:

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:soapenc="http://www.w3.org/2003/05/soap-encoding" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<soap:Fault>
<soap:Code>
<soap:Value>wsse:FailedAuthentication</soap:Value>
</soap:Code>
<soap:Reason>
<soap:Text xml:lang="en-US">Number of Targets in the message dont match number of Targets in receiver requirements</soap:Text>
</soap:Reason>
</soap:Fault>
</soap:Body>
</soap:Envelope>

Error Messages



<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:soapenc="http://www.w3.org/2003/05/soap-encoding" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<soap:Fault>
<soap:Code>
<soap:Value>wsse:FailedAuthentication</soap:Value>
</soap:Code>
<soap:Reason>
<soap:Text xml:lang="en-US">Number of Targets in the message dont match number of Targets in receiver requirements</soap:Text>
</soap:Reason>
</soap:Fault>
</soap:Body>
</soap:Envelope>


Steps to Reproduce



Configure the outgoing flow as attached and invoke SOAP service hosted in PRPC.


Root Cause



The current implementation does not support signing of the timestamp for Service SOAP.



Resolution



This capability is not supported for PRPC 6.3 SP1. Please contact your account manager for availability of the feature in future releases.
Suggest Edit

Published March 21, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us