Performing Import operation

1. Under Settings > Users/Groups/Roles > Search for the ranger user.
2. Click on the ranger user and change its role to Admin and save the changes.

• config-files
• scripts

The config-files contains the following:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <property>
    <name>authorization.migration.export.target_services</name>
    <value>HIVE,KAFKA</value>
  </property>
  <property>
    <name>authorization.migration.export.migration_objects</name>
    <value />
  </property>
  <property>
    <name>authorization.migration.export.output_file</name>
    <value>hdfs:///user/sentry/export-permissions/permissions.json</value>
  </property>
  <property>
    <name>authorization.migration.ingest.is_dry_run</name>
    <value>false</value>
  </property>
  <property>
    <name>authorization.migration.role.permissions</name>
    <value>true</value>
  </property>
  <property>
    <name>authorization.migration.translate.url.privileges</name>
    <value>false</value>
  </property>
  <property>
    <name>authorization.migration.ingest.merge.ifexists</name>
    <value>true</value>
  </property>
  <property>
    <name>authorization.migration.migrate.url.privileges</name>
    <value>true</value>
  </property>
</configuration>

For example:

/var/run/cloudera-scm-agent/process/<ranger-process-ID>-ranger-RANGER_ADMIN) to the location /opt/authz-ingest/config-files/ of the migration tool host.

Follow these steps to find the Ranger admin process directory:

• Execute the below command to get to the RANGER_ADMIN process:

ps -ef | grep proc_rangeradmin

• Search for -cp option from the above command output and look for

  "/var/run/cloudera-scm-agent/process/<ID>-ranger-RANGER_ADMIN"

If you have done SSL setup manually or in a different method, copy the filename which you created for truststores.

For example:

• 1. JAVA_HOME - Java home path used on the cluster
  2. RANGER_ADMIN_URL - Ranger Admin portal url
  3. RANGER_ADMIN_SSL_ENABLED - either true or false
  4. RANGER_ADMIN_TRUSTORE_PASSWORD - If Ranger is TLS/SSL enabled using Cloudera Manager AUTO-TLS, then the password can be found on the Ranger host /etc/hadoop/conf/ssl-client.xml property 'ssl.client.truststore.password'

Locate the property “authorization.migration.ranger.import.input_file” and provide the location of the transformed output file generated from Running the transform operation.

Example: file:///tmp/exportedRangerPolicies_transform.json

<property>

<name>authorization.migration.ranger.import.input_file</name>

If the KDC server is not installed in your environment or imported without the Kerberos authentication, you can skip this procedure and use the process provided for non-Kerberos authentication. Also if PAM auth is enabled in the target cluster then Kerberos authentication is recommended to import Ranger policies quickly.

• Find the Ranger admin keytab location and provide it in the following command:

export RANGER_ADMIN_KEYTAB_PATH=/path/to/ranger.keytab

In the CDEP cluster, Ranger keytab shall be available in the Ranger host location “/cdep/keytabs/rangeradmin.keytab” or under the Ranger admin process directory

“/var/run/cloudera-scm-agent/process/<ranger-process-ID>-ranger-RANGER_ADMIN” location.

Steps to find the Ranger admin process directory:

• Execute the following command to get to the RANGER_ADMIN process.

ps -ef | grep proc_rangeradmin

• Search for -cp option from the above command output and look for "/var/run/cloudera-scm-agent/process/<ID>-ranger-RANGER_ADMIN"

• If your Ranger node and migration node (target data lake Ranger node) are different, copy the Ranger keytab to the migration node (target data lake Ranger node).
• Run the below klist command on the migration node (target data lake Ranger node) to get the list of principals available in ${RANGER_ADMIN_KEYTAB_PATH}

• Run the below kinit command using the ${RANGER_ADMIN_KEYTAB_PATH} with rangeradmin/_HOST@REALM principle.
• Update the _HOST and the REALM correctly using the below command.

kinit -kt ${RANGER_ADMIN_KEYTAB_PATH} rangeradmin/_HOST@REALM

<property>
    <name>ranger.admin.username</name>
    <value>admin</value>
</property>
<property>
<name>authorization.migration.kerberos.authentication</name>
<value>false</value>
</property>

cd authz-ingest/scripts