Configuring HAWQ to use Ranger Policy Management

Your HAWQ installation includes the following HAWQ-related Ranger components:

  • Ranger Administrative UI
  • HAWQ Ranger Plug-in Service

The Ranger Administrative UI is installed when you install HDP. You configure the Ranger service itself through Ambari. You configure HAWQ-Ranger authorization policies through the Ranger Administrative UI, which you can access at http://<ranger-admin-node>:6080.

Installing or upgrading to HAWQ installs the HAWQ Ranger Plug-in Service, but neither configures nor registers the plug-in.

To use Ranger for managing HAWQ authentication events, you must first install and register several HAWQ JAR files on the Ranger Administration host. This one-time configuration establishes connectivity to your HAWQ cluster from the Ranger Administration host.

After registering the JAR files, you enable or disable Ranger integration in HAWQ by setting the hawq_acl_type configuration parameter. When Ranger is enabled, all access to HAWQ resources is controlled through Ranger security policies. The HAWQ Ranger Plug-in pre-populates Ranger with HAWQ policies to allow gpadmin superuser access to all resources. See Creating HAWQ Authorization Policies in Ranger for information about creating policies in Ranger.

Use the following procedures to register the HAWQ Ranger Plug-in Service and enable Ranger authorization for HAWQ.

Prerequisites

To use HAWQ Ranger integration, install a compatible Hadoop distribution and Apache Ranger 0.6. You must also have admin access to the Ranger Admin UI.

Step 1: Install Ranger Connectivity to HAWQ

  1. ssh into the Ranger Administration host as a user with root privileges:

    $ ssh root@<ranger-admin-node>
root@ranger-admin-node$

  2. Create the directory for the HAWQ JAR files:

    root@ranger-admin-node$ cd /usr/hdp/current/ranger-admin/ews/webapp/WEB-INF/classes/ranger-plugins
root@ranger-admin-node$ mkdir hawq

  3. Copy the necessary HAWQ JAR files (postgresql-9.1-901-1.jdbc4.jar and ranger-plugin-admin-<version>.jar) from the HAWQ master node to the new directory:

    root@ranger-admin-node$ scp <hawq-master>:/usr/local/hawq/ranger/lib/*.jar ./hawq

  4. Change the ownership of the new folder and JAR files to the ranger user:

    root@ranger-admin-node$ chown -R ranger:ranger hawq

  5. Configure Ranger connectivity to your HAWQ cluster with the enable-ranger-plugin.sh script. The command has the syntax:

    enable-ranger-plugin.sh -r <ranger_admin_node>:<ranger_port> -u <ranger_user> -p <ranger_password> [-h <hawq_master>:<hawq_port> -t <lookup_authentication_type> -s <hawq_kerberos_service_name>] -w <hawq_user> -q <hawq_password>

    Note: You can also enter the short form of the command: ./enable-ranger-plugin.sh -r and the script will prompt you for entries.

    1. Log in to the HAWQ master node as the gpadmin user, set up your HAWQ environment, and navigate to the HAWQ Ranger Plug-in bin directory:

      $ ssh gpadmin@master
gpadmin@master$ . /usr/local/greenplum_path.sh
gpadmin@master$ cd /usr/local/hawq/ranger/bin

    2. Execute the enable-ranger-plugin.sh script. You will provide different options for the script depending upon whether or not you have enabled Kerberos in your HAWQ cluster.

      If Kerberos is not enabled for Ranger:

      gpadmin@master$ ./enable-ranger-plugin.sh -r ranger_host:6080 -u admin -p admin -h hawq_master:5432 -w gpadmin -q gpadmin

RANGER URL  = ranger_host:6080
RANGER User = admin
RANGER Password = [*****]
HAWQ HOST = hawq_master
HAWQ PORT = 5432
HAWQ User = gpadmin
HAWQ Password = [*******]
HAWQ Lookup Authentication Type = simple
HAWQ Kerberos Service Name = postgres
HAWQ service definition was not found in Ranger Admin, creating it by uploading /usr/local/hawq_<version>/ranger/etc/ranger-servicedef-hawq.json
HAWQ service instance was not found in Ranger Admin, creating it.
Updated POLICY_MGR_URL to http://ranger_host:6080 in /usr/local/hawq_<version>/ranger/etc/rps.properties
Updated default value of JAVA_HOME to /usr/jdk64/jdk1.8.0_77 in /usr/local/hawq_<version>/ranger/etc/rps.properties

      If Kerberos is enabled for Ranger:

      Provide the -s option, specifying the <hawq_kerberos_service_name>; default is postgres. Also provide the -t option, specifying a <lookup_authentication_type> of kerberos. For example:

      gpadmin@master$ ./enable-ranger-plugin.sh -r ranger_host:6080 -u admin -p admin -h hawq_master:5432 -s postgres -t kerberos -w gpadmin -q gpadmin

      See Configure HAWQ for Kerberized Ranger for additional configuration required when Kerberos is enabled for Ranger.

    When the script completes, the default HAWQ service definition is registered in the Ranger Admin UI. This service definition is named hawq.

  6. Locate the pg_hba.conf file in the master directory of the HAWQ master node. To display the HAWQ master directory:

    gpadmin@master$ hawq config --show hawq_master_directory
GUC     : hawq_master_directory
Value   : /data/hawq/master

  7. Edit the pg_hba.conf file to configure HAWQ access for <hawq_user> on the <ranger-admin-node>. For example, you would add an entry similar to the following for the example enable-ranger-plugin.sh call above:

    host  all     gpadmin    ranger_host/32       trust

    And reload HAWQ configuration:

    gpadmin@master$ hawq stop cluster --reload

    Note: If you have enabled Kerberos user authentication for HAWQ, you may not need to create a pg_hba.conf entry, or your entry will differ. See Configure Ranger for Kerberized HAWQ for additional configuration information.

  8. Log in to the Ambari UI.

  9. Click the Ranger service in the left pane to display the Ranger Summary page, then select Quick Links > Ranger Admin UI.

  10. Log in to the Ranger Access Manager. Navigate to the HAWQ service and click the Edit button for the hawq service definition. Ensure that the Active Status is set to Enabled, and click Test Connection. You should receive a message that Ranger connected successfully. If the connection fails, verify the hawq service Config Properties, as well as your pg_hba.conf entries, and re-test the connection.

Step 2: Configure HAWQ to Use Ranger Policy Management

The default Ranger service definition for HAWQ assigns the HAWQ administrator (typically gpadmin) all privileges to all objects.

Once the connection between HAWQ and Ranger is configured, you may choose to set up policies for the HAWQ users according to the procedures in Creating HAWQ Authorization Policies in Ranger or enable Ranger with only the default policies.

Note: Any authorization defined using GRANT commands will no longer apply after enabling HAWQ Ranger. Enabling Ranger authorization for HAWQ with only the default policies defined provides access only to the gpadmin user.

  1. Log in to the Ambari UI, select the HAWQ Service, and then select the Configs tab.
  2. Select the Advanced tab, and then expand Custom hawq-site.
  3. Click Add Property… and add the new property, hawq_acl_type=ranger property. (If the property already exists, change its value from standalone (the default) to ranger.)
  4. Click Save to save your changes.
  5. Select Service Actions > Restart All and confirm that you want to restart the HAWQ cluster.

Step 3: (Optional) Register a Standby Ranger Plug-in Service

The HAWQ Ranger Plug-in Service runs on the HAWQ master node. If this service goes down, all HAWQ database operations will fail. Configure a highly available HAWQ Ranger Plug-in Service to eliminate possible downtime should this situation occur. The standby Ranger Plug-in Service runs on the HAWQ standby master node, utilizing the same port number as that when the service runs on the master node. To enable HAWQ Ranger high availability, you must register the standby Ranger Plug-in Service on the standby master node, and then restart the standby.

Configuring both Ranger Adminstration host and HAWQ Ranger Plug-in Service high availability is advised. However, Ranger Administration host high availability and HAWQ Ranger Plug-in Service high availability are independent; you can configure HAWQ Ranger Plug-in Service HA without configuring HA for the Ranger Administration host.

Prerequisites

Before you configure HAWQ Ranger authentication in high availability mode, ensure that you have:

  • (Optional) Configured the Ranger Admininstration host for high availability.

  • Configured a HAWQ standby master node for your HAWQ cluster.

    You must configure a standby master for your HAWQ deployment before enabling HAWQ Ranger high availability mode. If you have not configured your HAWQ standby master, follow the instructions in Adding a HAWQ Standby Master (if you manage your HAWQ cluster with Ambari) or Configuring Master Mirroring (for a command-line-managed HAWQ cluster).

  • Registered the HAWQ Ranger Plug-in Service on your HAWQ master node.

    The HAWQ Ranger Plug-in Service runs on the HAWQ master node. If you have not yet enabled the Ranger Plug-in Service, refer to Install Ranger Connectivity to HAWQ for registration instructions. (Optional) If you have configured Ranger Administration host HA, make sure to identify the Ranger Administration host HA proxy when you enable the plug-in.

Note: If you configured and registered the master HAWQ Ranger Plug-in Service before you initialized your HAWQ standby master node, you do not need to perform the steps in this section.

Procedure

  1. Synchronize the HAWQ Ranger Plug-in Service configuration files from the HAWQ master node to the standby master node by either manually copying the files, or by running enable-ranger-plugin.sh on the standby master. For example (where $GPHOME represents your base HAWQ install directory):

    gpadmin@master$ scp $GPHOME/ranger/etc/* gpadmin@standby:$GPHOME/ranger/etc/

    If you choose to execute enable-ranger-plugin.sh on the HAWQ standby master, provide the same arguments you used in your invocation of this command on the HAWQ master node:

    gpadmin@standby$ $GPHOME/ranger/bin/enable-ranger-plugin.sh -r <ranger_admin_node>:<ranger_port> -u <ranger_user> -p <ranger_password> -h <hawq_master>:<hawq_port> -w <hawq_user> -q <hawq_password>

  2. Restart the HAWQ standby master node. You will perform different procedures depending upon whether you manage your HAWQ cluster from the command line or you use Ambari to manage your cluster.

    If you manage your HAWQ cluster from the command line:

    gpadmin@master$ hawq stop standby
gpadmin@master$ hawq start standby

    If you manage your HAWQ cluster with Ambari:

    1. Follow the instructions in Removing the HAWQ Standby Master to remove the HAWQ standby master.
    2. Follow the instructions in Adding a HAWQ Standby Master to re-add the HAWQ standby master.

Displaying the Status of HAWQ/Ranger Integration

Determine the status of HAWQ/Ranger integration in your cluster by:

  • Identifying the access control method currently in place in your HAWQ cluster. If the hawq_acl_type server configuration parameter value is set to ranger, you have enabled Ranger authorization for HAWQ.

    gpadmin@master$ hawq config -s hawq_acl_type
GUC       : hawq_acl_type
Value     : ranger

  • Querying the state of your HAWQ cluster. If hawq state or Ambari HAWQ Service Check output identifies that the HAWQ Ranger Plug-in Service status is Active, the plug-in is up and running:

    gpadmin@master$ hawq state
...
20170327:16:35:06:508426 hawq_state:master:gpadmin-[INFO]:--   Current HAWQ acl type                         = ranger
20170327:16:35:06:508426 hawq_state:master:gpadmin-[INFO]:--   HAWQ master Ranger plugin service state       = Active
...

    If you have registered a standby Ranger Plug-in Service, hawq state also displays the status of that standby service:

    20170327:16:35:06:508426 hawq_state:master:gpadmin-[INFO]:--   HAWQ standby Ranger plugin service state      = Active

Custom Configuration

Configuration files for the HAWQ Ranger Plug-in Service are located in the $GPHOME/ranger/etc directory. These files include:

File Description
ranger-hawq-audit.xml HAWQ Ranger audit-related configuration, including the audit provider (log4j, Solr, HDFS) and provider-specific configuration
ranger-hawq-security.xml HAWQ Ranger service configuration, including the policy change polling interval
rps.properties HAWQ Ranger deployment-related configuration, including the HAWQ Ranger Plug-in Service port definition and JVM parameters

Any configuration changes you make after you have registered the HAWQ Ranger Plug-in require a restart of the service. You can either restart the HAWQ cluster or restart just the HAWQ Ranger Plug-in Service:

gpadmin@master$ /usr/local/hawq/ranger/bin/rps.sh stop
gpadmin@master$ /usr/local/hawq/ranger/bin/rps.sh start

Troubleshooting Ranger Configuration

If resource name lookup is not working in the Ranger Admin UI:

  1. Verify that the HAWQ Ranger plug-in JARs and JDBC driver have been copied to <ranger-admin-node>.
  2. Test the connection between the Ranger Admin UI and the HAWQ master node by clicking the edit icon associated with the active HAWQ service definition, then clicking the Config Properties: > Test Connection button.
  3. Verify that the HAWQ master node pg_hba.conf file includes a host entry for <ranger-admin-node>, HAWQ user (typically gpadmin).