Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

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.

How to set up two-way SSL for SOAP over HTTP using Rule-Connect-SOAP

Updated on September 13, 2021

These instructions apply exclusively to Process Commander systems supported by Apache Tomcat.

To prevent unauthorized access to your Web services, you can implement two-way SSL (Secure Socket Layer). Two-way SSL requires the Web services server to present a signed certificate to the client proving its identity, as well as requiring the client to present a signed certificate to the server verifying its identity.

If two-way SSL is not configured properly, no connection is made and an error similar to the following might be issued:

ssl error:
11:14:20,883 [ http8080-Processor7] (ivity.Invoke.Rule_Connect_SOAP) ERROR ADJSMNMP003DEV||Rule-Connect-SOAP.Data-ASI-V207-ASIService-.searchSpecialInstructions AcmeCo.Acme - SOAP service failed: PKIX path building failed: unable to find valid certification path to requested target
faultCode: {}Server.userException
faultString: PKIX path building failed: unable to find valid certification path to requested target
{}stackTrace: PKIX path building failed: unable to find valid certification path to requested target

This error occurs because two-way SSL requires both a client certificate and a server certificate.

Suggested approach

To initiate two-way SSL over HTTPS using Rule-Connect-SOAP, you need to configure the trust store and key store files, and then configure the client and server.

Configure the trust store and key store files

The trust store and key store files should already be configured. If not, your Web Services system administrator needs to perform the following steps.

1. Create and import the server certificate into the client trust store.

2. Create and import the client certificate into the server trust store.

See the instructions at the following link to complete steps 1 and 2: WWW

Server configuration

On the server, configure the HTTPS connector in Tomcat’s server.xml file ($CATALINA_HOME/conf/server.xml):

1. Uncomment the connector definition in the file. (By default it is commented out.)

2. Set the clientAuth attribute to ‘true’.

3. Enter values for the following attributes to point to their configured file locations:

  • keystoreFile
  • truststoreFile

4. Enter the appropriate passwords for the following attributes:

  • keystorePass
  • truststorePass

The updated connector definition in the server.xml file will be similar to the following:

<!-- Define a SSL HTTP/1.1 Connector on port 8443 -->

<Connector port="8443" maxHttpHeaderSize="8192"

maxThreads="150" minSpareThreads="25" maxSpareThreads="75"

enableLookups="false" disableUploadTimeout="true"

acceptCount="100" scheme="https" secure="true"

clientAuth="true" sslProtocol="TLS"




truststorePass=" server_truststore_pw_mypassword"/>

Relative filepaths for the keystoreFile and truststoreFile are resolved relative to the $CATALINA_HOME directory.

For Tomcat, the keystore password and the key password should be the same. This applies to the client keystore specified below as well. (For details, see the section entitled “Prepare the Certificate Keystore” in the Tomcat URL referenced above.)

Client configuration

On the client, add the following command line arguments to the Tomcat setenv.bat file: C:/tomcat/client_truststore.keystore client_truststore_pw_mypassword

where the values for these arguments are the file locations and the passwords.

For further details on this step, see the instructions at the following link:


Error reporting

Two-way SSL involves heavy HTTP traffic. If an error message displays, this traffic makes it difficult to determine where in the process the error occurred. To resolve this issue, set the following command line option in Process Commander:

For Sun JVMs:



Pega Platform 7.1.1 - 8.3.1 System Architect System/Cloud Ops Administrator Data Integration

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us