Skip to main content

Privacera Documentation

Table of ContentsTable of Contents

Configure service name for Databricks Spark plugin on Privacera Platform

By default in the 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 in the config/custom-vars/vars.databricks.plugin.yml file.

Note

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. From the navigation menu, select Access Management > Resource Policies.

  2. Create the repositories with your custom names. See Resource policies for more information.

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

    • The Active status is enabled/on.

    • The Common Name of the Certification = Ranger.

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

  4. Modify the DATABRICKS_SERVICE_NAME_PREFIX property to your custom service name prefix.

  5. Update Privacera Manager:

    ./privacera_manager.sh update

  6. Restart the cluster that is pointing to the updated init script.