How to enable TIBCO BusinessEvents 5.3 engine to use TLSv1.2 while connecting SSL enabled EMS 8.3
Article ID: KB0094772
Updated On:
| Products | Versions |
|---|---|
| DO NOT USE! - TIBCO BusinessEvents - Enterprise Edition | 5.3.0 |
Description
By default, BE 5.3 tries to connect to an EMS server using TLSv 1.0 . If EMS is configured to have an SSL connection and if it supports only TLSv1.2 cipher suites, then BE will throw the exception "SSL handshake failed : reason=no shared cipher" during the handshake process.
Environment
Product: TIBCO BusinessEvents Version: 5.3.x and Enterprise Messaging Service 8.3
OS: All Operating Systems
Resolution
The is caused by the TIBCrypt.jar bundled in BE 5.3.0. This has been found to be an older version of the JAR. EMS 8.3 comes with a new version of this JAR. We can enable BE to use TLSv1.2 after replacing the EMS's bundled copy of TIBCrypt.jar .
Delete TIBCrypt.jar from BE_HOME/lib/ext/tibco and copy tibcrypt.jar from EMS_HOME/lib to BE at the same location.
Delete TIBCrypt.jar from BE_HOME/lib/ext/tibco and copy tibcrypt.jar from EMS_HOME/lib to BE at the same location.
Issue/Introduction
TIBCO BusinessEvents (BE) engine throws "SSL handshake failed : reason=no shared cipher" exception during the handshake process while connecting to SSL enabled EMS.
Was this article helpful?
Yes
No
Powered by
