In the current implementation, ObjectStore.configureSSL throws an exception if TLS to the database is turned on (metastore.dbaccess.ssl.use.SSL) but a truststore file location (metastore.dbaccess.ssl.truststore.path) is not specified.
However, according to the JSSE (Java 8) documentation, the Java truststore file location system property (javax.net.ssl.trustStore) defaults to using the "jssecacerts, if it exists. Otherwise, cacerts" files. These are the default truststores that come with the Java installation and contain a list of well-known certificate authorities.
It was identified that one valid way of configuring TLS is by adding to these default files. In that case, no changes to the truststore properties are necessary. We should support this case by changing the following logic to remove the requirement for the truststore file location config property:
We should also loosen the requirement on the truststore password if the user decides to use the Java defaults