-
Type: Improvement
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 9.10
-
Component/s: Elasticsearch
-
Release Notes Summary:An Elasticsearch RestClient Truststore can now be configured.
-
Impact type:Configuration Change
-
Upgrade notes:
-
Sprint:nxFG 10.3.9
-
Story Points:2
The Elasticsearch RestClient currently allows a custom Keystore to be used. It should also allow a custom Truststore to be used as well.
By allowing a custom Elasticsearch RestClient Truststore to be specified, the configuration of a secure connection between the nuxeo-apb and the nuxeo-elasticsearch-apb on OpenShift is simplified and improved.
No longer does the nuxeo-elasticsearch-apb self-signed CA certificate need to be imported into the jvm-wide Nuxeo trustore. Instead, it can be imported into its own elasticsearch-specific truststore for direct use by Nuxeo. This also potentially eliminates the need in the nuxeo-apb to set ssl-related JVM system properties.
An SSL best practice is to use a specific SSLContext for each secure client connection rather than relying on the global, DefaultSSLContext which is configured via JVM system properties. In some cases, using JVM system properties to set keystore/truststore passwords is problematic because the passwords appear on the java entry in the process list.