Resolution:
Description:
============
While doing an EMS connection with SSL, the  BC logs error as:
>>>>
caused by: javax.naming.AuthenticationException: Not permitted: Failed to initialize SSL client: java.lang.RuntimeException: com.tibco.security.AXSecurityException: no certificate suitable for signing is available [Root exception is javax.jms.JMSSecurityException: Failed to initialize SSL client: java.lang.RuntimeException: com.tibco.security.AXSecurityException: no certificate suitable for signing is available]
<<<<

Symptoms:
=========
Configured correct set of certificates and they are getting "Test Connection" sucessfull for EMS under Application management> BusinessConnect > Configuration.

However when the BC Interior Server starts, it generates the error as:
>>>>
BW.BusinessConnect-Interior_Server Error [bw.logger] BW-EXT-LOG-100000 RuntimeBootsrtap:sInit Error connecting to JMS Server.Not permitted: Failed to connect to any server at: ssl://&ltxxxx>:8240, ssl://&ltxxxx>:8240 [Error: Failed to initialize SSL client: java.lang.RuntimeException: com.tibco.security.AXSecurityException: no certificate suitable for signing is available: url that returned this exception = SSL://&ltxxxx>:8240 ] . Attempting to reconnect
<<<<

Customer was able to connect via Designer with certificates but not through BusinessConnect. The same configuration works with BC 5X with no issues.

Environment:
==========
BC 6x.

Platforms
========
All

Resolution:
==========

BusinessConnect supports the use of multiple security vendors such as Sun and Entrust.  BC 5X only supported Entrust.  If BC 5.x worked in this environment  try changing the security provider as follows: Administrator&gtBusinessConnect&gtSystem Settings &gtActivated Protocol Plug-ins and Properties &gtBC> and change security provider to Entrust. By default it is using Sun. This property is used to set Tibcrypt's secure socket vendor for all outbound SSL connections.