Enabling SSL with Existing Certificates
If you want to enable SSL with existing certificates, and plan to use Ranger for authorization:
- Check the Enable SSL? box.
- Set Keystore
path, Keystore
password, and Keystore
type values.
The keystore path is similar to: /etc/security/nifi-certs/keystore.jks
- Set the Truststore
path, Truststore
password, and Truststore
type values.
The truststore path is similar to: /etc/security/nifi-certs/truststore.jks
- Check Clients need to authenticate? if you want to ensure that nodes in the cluster are authenticated and are required to have certificates that are trusted by the truststores.
- Check the Enable SSL? box.
- Set Keystore
path, Keystore
password, and Keystore
type values.
The keystore path is similar to: /etc/security/nifi-certs/keystore.jks
- Set the Truststore
path, Truststore
password, and Truststore
type values.
The truststore path is similar to: /etc/security/nifi-certs/truststore.jks
- Check Clients need to authenticate? to ensure that nodes in the cluster are authenticated and are required to have certificates that are trusted by the Truststores.
- Specify the Initial Admin Identity. The Initial Admin Identity is the
identity of an initial administrator and is granted access to the UI and has the
ability to create additional users, groups, and policies. This is a required value when you are not using the
Ranger plugin for NiFi for authorization.
The Initial Admin Identity format is CN=admin, OU=NIFI.
After you have added the Initial Admin Identity, you must immediately generate certificate for this user.
- Specify the Node
Identities. This indicates the identity of each node in a NiFi cluster
and allows clustered nodes to communicate. This is a required value when you are not using the
Ranger plugin for NiFi for
authorization.
<property name="Node Identity 1">CN=node1.fqdn, OU=NIFI</property> <property name="Node Identity 2">CN=node2.fqdn, OU=NIFI</property> <property name="Node Identity 3">CN=node3.fqdn, OU=NIFI</property>
Replace node1.fqdn, node2.fqdn, and node3.fqdn with their respective fully qualified domain names.