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

Connect SOAP fails SSL/TLS handshake, wrong version

SA-14558

Summary



SOAP connectors are using the TLS v1.2 encryption method when attempting to connect to a foreign service. The foreign system can only support up to TLS v1 causing SSLException.

Error Messages



[8/28/15 14:25:29:393 CDT] 00000045 SystemOut     O WebContainer : 2, WRITE: TLSv1.2 Handshake, length = 121
[8/28/15 14:25:29:394 CDT] 00000045 SystemOut     O WebContainer : 2, READ: TLSv1 Alert, length = 2
[8/28/15 14:25:29:394 CDT] 00000045 SystemOut     O WebContainer : 2, RECV TLSv1 ALERT:  fatal, unexpected_message
[8/28/15 14:25:29:394 CDT] 00000045 SystemOut     O WebContainer : 2, called closeSocket()
[8/28/15 14:25:29:394 CDT] 00000045 SystemOut     O WebContainer : 2, handling exception: javax.net.ssl.SSLException: Received fatal alert: unexpected_message

Steps to Reproduce



Not Applicable


Root Cause



A defect in Pegasystems’ code or rules

Resolution



Perform the following local-change: Comment out the following line from step # 8 of invokeAxis2 Activity

    client.getOptions().setProperty(com.pega.apache.axis2.transport.http.HTTPConstants.CUSTOM_PROTOCOL_HANDLER, authhttps);

 

Suggest Edit

Published October 1, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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