Configuring TLS/SSL for Navigator Metadata Server
Cloudera Navigator supports TLS/SSL encryption for network communications between the Navigator Metadata Server and clients, such as the web browser used for Cloudera Navigator console. Typically, TLS/SSL is configured for the entire cluster, so it is possible that the server key and certificate already exist on the specific host running the Navigator Metadata Server role. The assumption in the steps below is that the cluster is already configured for TLS/SSL and the security artifacts have already been obtained and deployed to the host running the Navigator Metadata Server role instance.
- Validate that the JDK on the Navigator Metadata Server host has certificates configured.
Navigator establishes trust for the TLS certificate used for network communication using the JDK on the local host. The JDK looks for certificates in three places:
- Location specified by java.net.ssl.truststore. This property can be set through the Navigator Metadata Server Advanced Configuration Snippet (Safety Valve) for cloudera-navigator.properties.
If the java.net.ssl.truststore location is set, the JDK ignores the default certificate locations.
- Validate the location of the keystore file on the host running the Navigator Metadata Server role instance.
For example, if TLS was enabled according to the instructions Configuring TLS Encryption for Cloudera Manager, the TLS keystore would be located in /opt/cloudera/security/pki. If the keystore isn't already on the Navigator Metadata Server host, generate one from the instructions in Generate TLS Certificates.
- Log in to the Cloudera Manager Admin Console.
- Select .
- Click the Configuration tab.
- Select .
- Select .
- Edit the following properties according to your cluster configuration.
Property Description Enable TLS/SSL for Navigator Metadata Server Encrypt network communications between clients and Navigator Metadata Server using TLS/SSL. TLS/SSL Keystore File Location The path to the keystore file containing the server private key and certificate. The keystore must be in JKS format. TLS/SSL Keystore File Password The password for the Navigator Metadata Server JKS keystore file. TLS/SSL Keystore Key Password The password for the private key contained in the JKS keystore.
- Click Save Changes.
- Restart the Navigator Metadata Server role.