Wire-level security encrypts data transmission between the nodes in your cluster.
Security features are turned off by default.
When you set up a cluster, run the
configure.sh script on each node that you want to add to the cluster. To enable security for the cluster, follow these steps in order:
configure.sh script with the
-secure -genkeys options on the first CLDB node in your cluster.
/opt/mapr/server/configure.sh -N <cluster_name> -secure -genkeys -Z <Zookeeper_node_list> -C <CLDB_node_list>
<CLDB_node_list> have the form
You must run
This command generates four files in the
cldb.keyfile to any node that has the CLDB or Zookeeper service installed.
ssl_truststorefiles to the
/opt/mapr/confdirectory of every node in the cluster.
Verify that the files from the previous step are owned by the user that runs cluster services. This user is
mapr by default. Also, the
ssl_keystore files must have their UNIX permission-mode bits set to
600, and the
ssl_truststore file must be readable to all users.
configure.sh -secure on each existing node in the cluster. The
-secure option indicates that the node is secure.
You must also do this on any nodes that you add to the cluster in the future.
ssl_truststore file to any client nodes outside the cluster.
If you run
maprlogin password (in this command,
password is literal text)
hadoop mfs -setnetworkencryption on <object> command for every table, file, and directory object in MapR-FS whose traffic you wish to encrypt.
The network encryption setting is inherited by new objects. Once encryption is turned on for a directory, all new directories, files, and tables created under that directory are automatically encrypted.
ssl_truststorefiles with the
/opt/mapr/server/manageSSLKeys.shtool. See Setting Up the Client for more information on MapR clients.
When you run the
configure.sh script at initial installation, but do not specify the
-genkeys option, the script generates a
ssl_keystore file for use by the web server for the MapR Control system. When the
configure.sh script is run with the
-genkeys option after initial installation, the system detects the existing
ssl_keystore file and exits with an error to prevent inadvertent deletion or reuse of the
ssl_keystore file. The error message will look similar to the following example:
/opt/mapr/server/configure.sh -secure -genkeys -C $CLDB_GRP -Z $ZK_GRP -RM $RM -HS $HISTORYSERVER
<hostname1>: Configuring Hadoop-2.x at /opt/mapr/hadoop/hadoop-2.x
<hostname1>: Done configuring Hadoop
<hostname1>: CLDB node list: <hostname1>:7222,<hostname2>:7222,<hostname3>:7222
<hostname1>: Zookeeper node list: <hostname1>:5181,<hostname2>:5181,<hostname3>:5181
<hostname1>: Node setup configuration: cldb fileserver historyserver nfs nodemanager resourcemanager webserver zookeeper
<hostname1>: Log can be found at: /opt/mapr/logs/configure.log
<hostname1>: /opt/mapr/conf/ssl_keystore already exists
<hostname1>: ERROR: could not generate ssl keys. See log file for more details
clush: <hostname1>: exited with exit code 1
ssl_keystorefile are unique to each node. In this case, manually delete the
ssl_keystorefile on each node, then run the command
ssl_keystorefile, run the command
configure.sh -genkeys -nocertsto preserve your customizations.
For general information on security tickets and certificates, see Tickets and Certificates.
After enabling security features for your cluster, the following behaviors change:
Components that have web UIs, such as the MapR Control System (MCS), Hive, and Oozie, require authentication.
Note that you must also complete the PAM Configuration to set up user authentication for MCS logins.
http:///f1 <access f1 in default cluster>
In addition, several open source components require further configuration.
To disable security features for your cluster:
configure.sh script with the
-unsecure option and specify the CLDB and ZooKeeper nodes.
configure.sh -unsecure -C <CLDB_Node> -Z <ZK_Node>
mapr-clusters.conf, the cluster is changed from