EMS 8.4 Java client has been redesigned to remove dependency on the legacy tibcrypt.jar library and is now completely dependent on the standard JSSE. When using the .jks file store, it is not required for passing an alias name so as to set the client side identity ( private key & public certificate ).
Issue/Introduction
Up to EMS 8.3.0 Java client API do do not have provision to set the client side identity (private key & public certifcate) by passing an alias name. But from EMS 8.4.0 Java API client it is not required to pass the alias
Environment
ALL
Resolution
We have a jks keystore that contains multiple aliases, only one of them has its issuer trusted by the EMS server, the Java client is able to pick up the right alias -- according to the trusted certificate list sent from server during the SSL handshake.
Here are the test steps:
# EMS server configuration ( The server does NOT have to be 8.4, we tried it with 8.2 and 8., and it worked well )