Overview 

Pega Platform™ '26.1 introduced changes to the SOAP connector integration framework due to architectural refactoring. The refactoring included an upgrade of the Apache Axis2 open source libraries from v1.6.2 to v2.0. It also included an upgrade of the Apache HttpClient from Commons v3 to HttpComponents v5.

Symptoms and Resolutions

1. Broken TLS/mTLS certificate validation

Symptom

A SOAP connector configured with a Security Profile does not apply the expected keystore and truststore settings. When the remote server requests a client certificate, no certificate is sent and the TLS handshake is rejected with handshake_failure.

Resolution

2. Broken WS-Security password decoding

Symptom

After updating to Pega Platform 26.1.1, SOAP connectors fail with invalid credentials when the WS-Security profile password uses GRS syntax and the profile is referenced through data pages. The username continues to resolve correctly, and directly entering the password works.

Resolution

3. WS-Security signature corruption 

Symptom

Digital signature validation can fail because the outgoing SOAP message is structurally changed after the SAML assertion is signed.

Resolution

4. Missing WS-Addressing SOAP headers

Symptom

Two related behaviors are reported:

• Required WS-Addressing headers such as wsa:Action, wsa:To, and wsa:ReplyTo are not injected into outbound requests even when WS-Addressing is enabled.
• SOAP fault responses containing WS-Addressing headers with mustUnderstand="1" are not processed correctly.

Resolution

5. Non-working proxy configuration

Symptom

For SOAP endpoints accessed through a proxy server, the connection must use pyProxySettingsForSOAP. Proxy Basic Authentication fails when pyProxyDomain is null despite other proxy details being correct.

Resolution

6. Corrupted SOAP response XML 

Symptom

The external system returned a successful HTTP 200 response, but Pega failed while parsing the XML. Although the XML was valid, the presence of similar namespace prefixes (xmlns:com and xmlns:communi) caused Pega’s internal SAX parser to identify them as duplicate namespace declarations, resulting in the parsing failure.

Resolution

Root Cause

• Migration to HttpClient v5 broke certificate handling
• InvokeAxis2 deprecation requires refactoring of custom execution code
• Axis2 WS-Addressing module failed to load from Pega classpath
• Proxy domain parameter is set when not configured
• Axis2 response processing corrupted XML
• WS-Security password expressions failed to resolve