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

SOAP Authentication fails when multibyte char in request

SA-5896

Summary



Signature verification fails when SOAP message contains multibyte-Chinese characters when consumed using Connect-SOAP in PRPC 6.2 SP2.

Error Messages



<soap:Body>

    <soap:Fault>
        <soap:Code>
            <soap:Value>wsse:FailedAuthentication</soap:Value>
        </soap:Code>
        <soap:Reason>
            <soap:Text xml:lang="en-US">com.sun.xml.wss.impl.WssSoapFaultException: Signature verification failed</soap:Text>
        </soap:Reason>
    
</soap:Fault>
</soap:Body>


Steps to Reproduce

  1. Create a SOAP connector in PRPC with signature configured in outflow of WS-Security.
  2. Consume the external service using Pega Connector.
  3. Pass multibyte characters, for example: 正體字/繁體字 to the request.

Root Cause



A defect in Pegasystems’ code or rules:
Platform-specific request bytes were passed 
to the third-party web services code when signature is enabled instead of UTF bytes.

Resolution



Apply HFix-20609.

    Published November 10, 2016 - Updated October 8, 2020

    Was this useful?

    0% found this useful

    Have a question? Get answers now.

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

    Did you find this content helpful?

    Want to help us improve this content?

    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