Privacera Platform master publication

Configure service name for Databricks Spark plugin
:

By default in Privacera Portal, all policies are defined in privacera_hive under Access Management > Resource Policies. This page explains how to configure a custom Ranger repository.

For custom repositories, you will change the DATABRICKS_SERVICE_NAME_PREFIX property in the config/custom-vars/vars.databricks.plugin.yml file. (This property is applicable only for the Databricks FGAC plugin.)

Your service repositories will be named using this value as a prefix:

  • Hive: DATABRICKS_SERVICE_NAME_PREFIX_hive.

  • S3: DATABRICKS_SERVICE_NAME_PREFIX_s3.

  • ADLS: DATABRICKS_SERVICE_NAME_PREFIX_adls.

  • Files: DATABRICKS_SERVICE_NAME_PREFIX_files.

For example, if your DATABRICKS_SERVICE_NAME_PREFIX is dev your policies would be named the following:

dev_hive
dev_s3
dev_adls
dev_files                 

To customize a new service name:

  1. In the Privacera Portal, under Access Management > Resource Policies, create the repositories with your custom names.

    When creating the policies:

    • Make sure the Username and Password fields have valid values.

    • The Active status is enabled/on.

    • The Common Name of the Certification= Ranger.

    Learn more about how to configure Resource Policies

  2. Open the config/custom-vars/vars.databricks.plugin.yml file.

    Modify the DATABRICKS_SERVICE_NAME_PREFIX property to your custom service name prefix.

  3. Update Privacera Manager by running the following script:

    ./privacera_manager.sh update
                            

    Then restart the cluster which is pointing to updated init script.