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.
- 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.
Note: After TLS/SSL is enabled, Cloudera Manager links to the Cloudera Navigator console use
HTTPS rather than unencrypted HTTP.
Page generated July 25, 2018.
<< Configuring TLS/SSL for Navigator Audit Server | ©2016 Cloudera, Inc. All rights reserved | Configuring TLS/SSL for Kafka (Navigator Event Broker) >> |
Terms and Conditions Privacy Policy |