Skip to main content

Privacera Documentation

Table of ContentsTable of Contents

Databricks SQL connector for PolicySync on Privacera Platform

This topic shows how to configure access control for Databricks SQL.

Generalized approach for implementing PolicySync

To help you reach compliance, Privacera PolicySync distributes your defined access management policies to the third-party datasources you connect to Privacera.

Use this generalized approach for implementing PolicySync.

  1. Understand how PolicySync works and how it is configured. See PolicySync design and configuration on Privacera Platform.

  2. Decide which PolicySync topology best suits your needs:

  3. Create the required, basic PolicySync configuration. See Required basic PolicySync topology: always at least one connector instance

  4. Examine the BASIC and ADVANCED properties, decide which features you want to implement, and set the necessary values in the YAML property file.

Connector name: databricks-sql-analytics

When you create the connector as detailed in PolicySync design and configuration on Privacera Platform, use the following reserved word for the name of the connector:


In formal syntax shown in Connector instance directory/file structure replace <ConnectorName> with the above and in the example in Required basic PolicySync topology: always at least one connector instance, replace postgres with the above.


Ensure the following prerequisites are met:

  • Create an SQL warehouse in Databricks SQL with a user having admin privileges. For more information, see Databricks documentation.

  • As you configure the warehouse make a note of the following values, which you to specify in the PolicySync properties for Databricks SQL :

    • Host URL

    • JDBC URL

    • SQL endpoint token

    • Database List