Cloudera Enterprise 5.15.x | Other versions

Configuring TLS/SSL for Oozie

Minimum Required Role: Configurator (also provided by Cluster Administrator, Full Administrator)

Before You Begin

Keystores for Oozie must be readable by the oozie user. This could be a copy of the Hadoop services' keystore with permissions 0440 and owned by the oozie group.
Truststores must have permissions 0444 (that is, readable by all).
Specify absolute paths to the keystore and truststore files. These settings apply to all hosts on which daemon roles of the Oozie service run. Therefore, the paths you choose must be valid on all hosts.
In case there is a DataNode and an Oozie server running on the same host, they can use the same certificate.

For more information on obtaining signed certificates and creating keystores, see Encrypting Data in Transit (TLS/SSL). You can also view the upstream documentation located here.

Important:

This configuration process can be completed using either Cloudera Manager or the command-line instructions.
This information applies specifically to CDH 5.15.0. If you use an earlier version of CDH, see the documentation for that version located at Cloudera Documentation.

Using Cloudera Manager

The steps for configuring and enabling Hadoop TLS/SSL for Oozie are as follows:

Open the Cloudera Manager Admin Console and go to the Oozie service.
Click the Configuration tab.
Select Scope > All.
Select Category > All.
In the Search field, type TLS/SSL to show the Oozie TLS/SSL properties.

Edit the following TLS/SSL properties according to your cluster configuration.

Table 1. Oozie TLS/SSL Properties
Property	Description
Enable TLS/SSL for Oozie	Check this field to enable TLS/SSL for Oozie.
Oozie TLS/SSL Server Keystore File Location	Location of the keystore file on the local file system.
Oozie TLS/SSL Server JKS Keystore File Password	Password for the keystore.

Click Save Changes.
Restart the Oozie service.

Using the Command Line

To configure the Oozie server to use TLS/SSL:

Stop Oozie by running
```
sudo /sbin/service oozie stop
```
To enable TLS/SSL, set the MapReduce version that the Oozie server should work with using the alternatives command.
Note: The alternatives command is only available on RHEL systems. For SLES, Ubuntu and Debian systems, the command is update-alternatives.
For RHEL systems, to use YARN with TLS/SSL:
```
alternatives --set oozie-tomcat-conf /etc/oozie/tomcat-conf.https
```
For RHEL systems, to use MapReduce (MRv1) with TLS/SSL:
```
alternatives --set oozie-tomcat-conf /etc/oozie/tomcat-conf.https.mr1
```
Important:
The OOZIE_HTTPS_KEYSTORE_PASS variable must be the same as the password used when creating the keystore file. If you used a password other than password, you'll have to change the value of the OOZIE_HTTPS_KEYSTORE_PASS variable in this file.
Start Oozie by running
```
sudo /sbin/service oozie start
```

Connect to the Oozie Web UI using TLS/SSL (HTTPS)

Use https://oozie.server.hostname:11443/oozie though most browsers should automatically redirect you if you use http://oozie.server.hostname:11000/oozie.

Additional Considerations when Configuring TLS/SSL for Oozie HA

To allow clients to talk to Oozie servers (the target servers) through the load balancer using TLS/SSL, Configure the load balancer for TLS/SSL pass-through, which means the load balancer does not perform encryption/decryption but simply passes traffic from clients and servers to the appropriate target host. See documentation for your load balancer for details.

Page generated May 18, 2018.