Importing Sentry permissions into Ranger

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:

authorization-migration-site.xml

ranger-hive-security.xml

ranger-kafka-security.xml

ranger-plugin-policymgr-ssl.xml

/opt/authz-ingest/config-files/ of the migration tool host.

Steps to find the ranger admin process directory:

• • Execute the below command to get 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: cp /path/to/cm-auto-global_truststore.jks /opt/authz-ingest/config-files/

• JAVA_HOME - Java home path used on the cluster
• RANGER_ADMIN_URL - Ranger Admin portal url
• RANGER_ADMIN_SSL_ENABLED - either true or false
• 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'

EXAMPLE:

export JAVA_HOME=/usr/java/jdk1.8.0_232-cloudera/

export RANGER_ADMIN_URL=<ranger admin url with port>

export RANGER_ADMIN_SSL_ENABLED=<true or false>

export RANGER_ADMIN_TRUSTORE_PASSWORD=<ssl.client.truststore.password>

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

   export RANGER_ADMIN_KEYTAB_PATH=/path/to/rangeradmin.keytab

   In the CDEP cluster ranger keytab shall be available in the “/cdep/keytabs/rangeradmin.keytab” or under the ranger admin process directory “/var/run/cloudera-scm-agent/process/<ranger-process-number>-ranger-RANGER_ADMIN” location.

   Steps to find the ranger admin process directory:

   • Execute the below command to get 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 are different, copy the ranger keytab to the migration node.

   On the migration node run the following klist command to fetch a list of principals available in

   ${RANGER_ADMIN_KEYTAB_PATH}

   klist -kt ${RANGER_ADMIN_KEYTAB_PATH}

   Run the following kinitcommand using

   ${RANGER_ADMIN_KEYTAB_PATH} with rangeradmin/_HOST@REALM principle.

   Update _HOST and REALM using the following command:

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

<property>

<name>authorization.migration.export.output_file</name>

<value>file:///root/permissions.json</value>

</property>

<property>

<name>authorization.migration.create.s3.policy</name>

<value>true</value>

</property>

<property>

<name>authorization.migration.target.s3.bucket.name</name>

<value>bucket_name</value>

</property>

<property>

<name>authorization.migration.translate.url.privileges</name>

<value>true</value>

</property>

<property>

<name>authorization.migration.migrate.url.privileges</name>

<value>true</value>

</property>

<property>

<name>authorization.migration.destination.location.prefix</name>

<value>s3a://mybucket</value>

</property>

<property>

<name>authorization.migration.translate.user</name>

<value>true</value>

</property>

<property>

<name>authorization.migration.usermap.file.path</name>

<value>file:///root/UserMapping.json</value>

</property>

Use the following information to provide the valid user mapping:

Format:

=> For the JSON file format we can have multiple users also in the JSON object formatted like :

{“testuser1”:”testuser1@host.com”, “testuser2”:”testuser2@host.com”}

=> And with the CSV format, it's pipe-delimited with one entry per line.

testuser1,testuser1@host.com

testuser2,testuser2@host.com

By default, this feature is disabled by setting the below value to false.

<property>
    <name>authorization.migration.skip.owner.policy</name>
    <value>true</value>
 		 </property>

cd authz-ingest/scripts

sh authz-import.sh

A confirmation message appears.

"Ingesting Ranger policies finished successfully"

"Ingesting of permissions to Ranger service is complete"