If Hotrod Server encryption's require-ssl-client-auth is set to true, <truststore .. /> existence must be checked ----------------------------------------------------------------------------------------------------------------- Key: ISPN-4313 URL: https://issues.jboss.org/browse/ISPN-4313 Project: Infinispan Issue Type: Bug Components: Configuration, Security, Server Affects Versions: 7.0.0.Alpha4 Reporter: Vijay Bhaskar Chintalapati Assignee: Tristan Tarrant Priority: Critical Fix For: 7.0.0.Alpha5 Currently the Infinispan Server can be configured with SSL encryption such that it requires the client to authenticate itself to the server for the purposes of encryption. This can be done by setting the attribute require-ssl-client-auth="true" as shown below. &nbsp;&nbsp;&nbsp;&nbsp;<hotrod-connector socket-binding="hotrod" cache-container="security"> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;.... &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<encryption security-realm="ApplicationRealm" require-ssl-client-auth="true"/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;.... &nbsp;&nbsp;&nbsp;&nbsp;</hotrod> But when that attribute is set to "true" a check should be enforced to check the existence of the the <truststore .. /> element exists in secruity-realm's <authentication>. If the check on the configuration fails, the server should throw and error on bootup rather than fail when client connections start to come in. Currently when the require-ssl-client-auth="true" and there is no <truststore../> configured, client connections fail and the exception below is thrown in the server's logs: javax.net.ssl.SSLHandshakeException: null cert chain