SSL Security for HttpFS

About this task

You can configure SSL (HTTPS) for HttpFS with or without certificate-based authentication for HttpFS. Use ssl_keystore and ssl_truststore, which are generated automatically for a secure cluster in /opt/mapr/conf/. Note: When using SSL on non-secure clusters, you need to manually generate keystore and truststore.

Procedure

To preserve the original version, rename the existing server.xml file (/opt/mapr/httpfs/httpfs-1.0/share/hadoop/httpfs/tomcat/conf/server.xml) to server.xml.orig.
```
sudo cp /opt/mapr/httpfs/httpfs-1.0/share/hadoop/httpfs/tomcat/conf/server.xml 
/opt/mapr/httpfs/httpfs-1.0/share/hadoop/httpfs/tomcat/conf/server.xml.orig
```

Replace the contents of server.xml with the contents of server.xml.https.

sudo cp /opt/mapr/httpfs/httpfs-1.0/share/hadoop/httpfs/tomcat/conf/server.xml.https 
/opt/mapr/httpfs/httpfs-1.0/share/hadoop/httpfs/tomcat/conf/server.xml

To enable SSL without certificate-based authentication, set the clientAuth attribute to "false" and set properties related to keystore and truststore (on a secure cluster, the defaults are already set properly) in server.xml (/opt/mapr/httpfs/httpfs-1.0/share/hadoop/httpfs/tomcat/conf/server.xml).
For example:
```
<Connector port="${httpfs.http.port}" SSLEnabled="true"
maxThreads="150" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS"
keystoreFile="/opt/mapr/conf/ssl_keystore"
keystorePass="<ssl-keystore-password>"
truststoreFile="/opt/mapr/conf/ssl_truststore"
truststorePass="<ssl-keystore-password>"/>
```

To enable certificate-based authentication, perform the following steps:

Verify that the clientAuth attribute is set to "true" and set properties related to keystore and trustore in server.xml (/opt/mapr/httpfs/httpfs-1.0/share/hadoop/httpfs/tomcat/conf/server.xml).

For example:

<Connector port="${httpfs.http.port}" SSLEnabled="true"
maxThreads="150" scheme="https" secure="true" clientAuth="true" sslProtocol="TLS"
keystoreFile="/opt/mapr/conf/ssl_keystore"
keystorePass="<ssl-keystore-password>"
truststoreFile="/opt/mapr/conf/ssl_truststore"
truststorePass="<ssl-keystore-password>"/>

In web.xml (/opt/mapr/httpfs/httpfs-1.0/share/hadoop/httpfs/tomcat/webapps/webhdfs/WEB-INF/web.xml), un-comment the following section:

<security-constraint>
           <web-resource-collection>
                <web-resource-name>Protected Context</web-resource-name>
                <url-pattern>/*</url-pattern>
           </web-resource-collection>
           <auth-constraint>
                <role-name>sample</role-name>
           </auth-constraint>
           <user-data-constraint>
                <transport-guarantee>CONFIDENTIAL</transport-guarantee>
           </user-data-constraint>
</security-constraint>
                
<security-role>
           <role-name>sample</role-name>
</security-role>
                
<login-config>
           <auth-method>CLIENT-CERT</auth-method>
</login-config>

Verify that tomcat-users.xml (/opt/mapr/httpfs/httpfs-1.0/share/hadoop/httpfs/tomcat/conf/tomcat-users.xml) contains the roles and users in the certificates.
```
<tomcat-users> 
         <role rolename="sample"/> 
         <user name="CN=<hostname>" password="null" roles="sample" /> 
</tomcat-users>
```
NOTE: The name value should include information from your certificate. For example, <tomcat-users> <role rolename="sample"/> <user name="CN=www.mapr.com, OU=mapr, O=mapr, L=San Jose, ST=San Jose, C=CA" password="null" roles="sample" /> </tomcat-users> You can run the following command to view the contents of the certificate file: openssl x509 -text -in /opt/mapr/hue/hue-<version>/cert.pem
```
<tomcat-users>
         <role rolename="sample"/>
         <user name="CN=www.mapr.com, OU=mapr, O=mapr, L=San Jose, 
             ST=San Jose, C=CA" password="null" roles="sample" />
</tomcat-users>  
```

Restart the HttpFS server.

maprcli node services -name httpfs -action restart -nodes <space delimited list of nodes>

Run one of the following curl commands to check that HTTPS is enabled. These commands fetch the file some_file.txt from MapR file system under /user/mapr and attempt to open it securely over HTTPS.
- To check if HTTPS is enabled, run the following command (which differs for non-secure and secure clusters):
  - For non-secure clusters:
```
curl -k "https://localhost:14000/webhdfs/v1/user/mapr/some_file.txt?
op=open&user.name=mapr" 
```
  - For secure clusters:
```
curl -u <user_name> -k 
"https://localhost:14000/webhdfs/v1/user/mapr/some_file.txt? 
op=open"
```
- If you configured Hue to use SSL encryption with certificate-based authentication for communication with HttpFS, run the following command (which differs for non-secure and secure clusters):
  - For non-secure clusters:
```
curl -k 
--cert /opt/mapr/hue/hue-<version>/cert.pem 
--key /opt/mapr/hue/hue-<version>/hue_private_keystore.pem 
"https://localhost:14000/webhdfs/v1/user/mapr/some_file.txt?
op=open&user.name=mapr"
```
  - For secure clusters:
```
curl -u <user_name> -k 
--cert /opt/mapr/hue/hue-<version>/cert.pem 
--key /opt/mapr/hue/hue-<version>/hue_private_keystore.pem 
"https://localhost:14000/webhdfs/v1/user/mapr/some_file.txt? 
op=open"
```