Skip to main content

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

Secure the transport layer in integrations

Updated on April 6, 2022

Learn how your Pega Platform application handles REST and SOAP connector rules that point to an SSL-enabled endpoint.

When a customer has a Connector rule for an HTTP-based protocol such as SOAP and REST, they might point to an SSL-enabled ("https") endpoint. The service that the endpoint connects to provides an SSL certificate in order to identify itself and secure the connection.

Pega Platform relies on the Application Server in order to "trust" the certificate that another service provided. When Pega Platform is deployed in Tomcat, this usually means that the default java truststore is in use. IBM WebSphere has its own truststore that is controlled in the Admin Console.

When the certificate provided by a service is not in the truststore, or otherwise not trusted (for instance, it is out of date or issued to a different organization), Pega Platform cannot complete the connection and an exception such as "Peer not authenticated" results.

It is the responsibility of the customer to ensure that the application server's truststore is set up correctly.

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