Support Article

403 Forbidden when using 2-way SSL with Connect-SOAP



2 way SSL using Dynamic outbound endpoint SSL is configured in WebSphere. When Connect-SOAP is configured to call a 2 way SSL it throws '403 Error: Forbidden' error.

Error Messages

Caused by: 
com.pega.apache.axis2.AxisFault: Transport error: 403 Error: Forbidden
    at com.pega.apache.axis2.transport.http.HTTPSender.handleResponse(
    at com.pega.apache.axis2.transport.http.HTTPSender.sendViaPost(
    at com.pega.apache.axis2.transport.http.HTTPSender.send(

Steps to Reproduce

    1. Configure 2 way SSL using Dynamic outbound endpoint SSL configuration in WebSphere.
    2. Configure Connect-SOAP in PRPC & invoke it.
    3. Check the log for the error message.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules in 5.4 SP1


This configuration is working fine in PRPC version 6.3 SP1.

Published February 3, 2015 — Updated January 31, 2016

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.