Authentication methods - Precisely Data Integrity Suite

Data Integrity Suite
Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2026

This section provides you the different authentication method used for Databricks in Data Integrity Suite.

Table 1. Authentication type
Field Description
Authentication method Select the authentication method to use for connecting to Databricks. Two options are available:
  • Regular: Uses standard token authentication.
  • Key Vault: Uses credentials stored securely in a key vault for enhanced security.
When regular authentication method is used, configure the following fields
Authentication token Specifies the access token for connecting to the Databricks workspace. Ensure that you generate and enter a valid token to successfully establish and secure the connection. Example: dapi1234567890abcdef1234567890abcdef
Note: You can either generate a token or contact your Databricks administrator if you do not have an authentication token.
Processing Environment for Cataloging Specifies the environment used for managing and organizing data catalogs. It provides two options:
  • Databricks Cluster: Select this option if you are using a Databricks cluster for data processing and cataloging. If this option is selected, also specify the relevant Databricks cluster. Example: Cluster-1
    • Catalog: Specifies name of the catalog where data is stored and managed. The default value is hive_metastore.
  • Databricks SQL Warehouse: Choose this option if you are utilizing a Databricks SQL Warehouse for data management and querying, also specify the relevant Databricks SQL warehouse. Example: SQLWarehouse-1.
    • Catalog: Specifies name of the catalog where data is stored and managed. The default value is hive_metastore.
  • Databricks Notebooks: Executes cataloging operations using Databricks Notebooks, which are collaborative, interactive environments within Databricks
    • Username: The email ID of the Databricks user or service principal. This is a mandatory field.
    • Directory Filter: Restricts cataloging to specific directories or workspace paths within the Databricks workspace. Specify one or more workspace path patterns using forward slashes (/) to limit the cataloging scope to relevant notebook assets. This is a mandatory field. The filter supports:
      • Exact folder paths
      • Wildcard matching
      • Recursive folder matching
      • Multiple comma-separated path patterns

      By default, Databricks user notebooks are typically stored under: /Users/<email-id>/

      Examples:

      • /Users/<email-id>/** : Catalogs all folders and notebooks under the specified user workspace path. ** indicates recursive matching for all folders and notebooks.

      • /Users/<email-id>/Folder1: Catalogs all notebooks within the specific folder Folder1.
      • /Users/<email-id>/Folder1,/Users/<email-id>/Folder2 : Catalogs notebooks from multiple specified folders.