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

2-way SSL not working :Transport error : 401 Error: Unauthorized



User cannot configure 2-way SSL for Connect-SOAP.

Error Messages

2015-04-22 14:31:56,529 [] [  STANDARD] [                    ] [] (ngineinterface.service.HttpAPI) ERROR: PRRuntimeError
 at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(
 at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivitiesAlt(
 at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.runActivities(
 at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(
 at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(
 at java.lang.reflect.Method.invoke(
 at java.util.concurrent.ThreadPoolExecutor.runWorker(
 at java.util.concurrent.ThreadPoolExecutor$
Caused by: SOAP service failed
 at com.pegarules.generated.activity.ra_action_invokeaxis2_ab4bacc4d22ff691fd98ed821335eb56.step15_circum0(
 at com.pegarules.generated.activity.ra_action_invokeaxis2_ab4bacc4d22ff691fd98ed821335eb56.perform(
 at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
 at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
 at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(
 ... 50 more
Caused by: com.pega.apache.axis2.AxisFault: Transport error: 401 Error: Unauthorized
 at com.pega.apache.axis2.transport.http.HTTPSender.sendViaPost(
 at com.pega.apache.axis2.transport.http.HTTPSender.send(

Steps to Reproduce

Run activity to call Connect-SOAP.

Root Cause

The root cause of this problem is defect/misconfiguration in the operating environment. The SSL connectivity between the Pega node and the external webservice endpoint is broken. This error indicates that the signer certificate and each of its intermediate certificates in the chain from the specified target host (external SOAP Endpoint) has not been located in the client Pega node’s (JVM’s) truststore.
When using the certificate from another entity (JVM), make sure to use the certificate chain to obtain the root CA certificate. The certificate chain, also known as the certification path, is a list of certificates used to authenticate an entity (JVM). The chain, or path, begins with the certificate of that entity, and each certificate in the chain is signed by the entity identified by the next certificate in the chain. The chain terminates with a root CA certificate. The root CA certificate is always signed by the CA itself. The signatures of all certificates in the chain must be verified until the root CA certificate is reached.



This issue is resolved through the following local change:

Ensure that the signer certificates and each of its intermediate certificates in the certification path are imported to the Pega IBM Websphere JVM’s truststore.

The same should be done for all the Websphere JVMs participating in SSL communication on your PRPC cluster.

Published March 10, 2016 - 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