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

WS-Security profile of Connect-Soap is not working correctly



A WSDL file from a different system is provided. The end point URL is a HTTPS request. Connect-Soap is used to receive the request. A certificate in CRT format and CA_Root.jks file is provided.
User converts the CRT file into JKS format, creates a keystore rule and uploads the converted file in the keystore rule. Then the user creates a web service security profile and mentions the keystore created in keystore and truststore field in the keystore tab of security profile. On submitting the request without mentioning any security profile an error is encountered.

Error Messages

pySoapFaultReason: PKIX path building failed: unable to find valid certification path to requested target .
pyInvocationException: Java Object:

Steps to Reproduce

1. Create a Connect SOAP rule
2. Using the advanced tab of the SOAP rule, configure the security profile.
3. Import the keystore file in the Keystore tab of the Security profile.
4. Using the secured service endpoint that is the service running on HTTPS, invoke the rule from an activity.

Root Cause

While executing the activity which is using Connect SOAP rule, security profile is not selected and WS security is checked.


This issue is resolved by mentioning the security profile and unchecking the WS Security checkbox, which allows the Connect SOAP rule to use SSL to complete the handshake with the service.
Selecting the WS Security results in the usage of web service security which is another level of security and not required in this case.

Published June 29, 2015 - 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