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 details on the authentication methods available for the AI Catalog datasource when using MCP / AI Agent discovery mode in Data Integrity Suite.

Note: Authentication methods in this section apply to MCP / AI Agent mode only. One authentication method applies to all MCP server endpoints and AI agent endpoints within a single connection. If different endpoints require different credentials, create a separate connection for each.
Table 1.
Authentication Method Description
No Authentication No credentials are sent. Use this method when all configured MCP server and AI agent endpoints are accessible without authentication (for example, on an internal network).
API Key Sends a static API key in a configurable HTTP request header. Provide the following fields:
  • Key value — the API key string.
  • Header name — the HTTP header to send the key in. Default is X-API-Key.
Bearer Token Sends a token as Authorization: Bearer <token> on every request. Provide the following field:
  • Token value — a valid JWT, personal access token, or session token with read access to the configured endpoints.
OAuth2 Client Credentials (API Key + Secret) Exchanges a client credential for a Bearer token before each harvest run using the OAuth2 client credentials grant. Provide the following fields:
  • Credentials — Base64-encoded API_KEY:API_SECRET.
  • Token URL — the OAuth2 token endpoint used to obtain the access token.
OAuth2 Authorization Code (refresh token) Uses a pre-issued refresh token to obtain a new access token before each harvest run. A browser OAuth2 flow is not supported; you must obtain the refresh token manually. Provide the following fields:
  • Client ID — the OAuth2 client identifier.
  • Client Secret — the OAuth2 client secret.
  • Refresh Token — a long-lived refresh token for a user or service account with read access to the endpoints.
  • Token URL — the OAuth2 token endpoint. This can be auto-discovered from the MCP server's WWW-Authenticate response header.
Basic (Username / Password) Sends credentials as Authorization: Basic <base64(username:password)> on every request. Provide the following fields:
  • Username — the account username.
  • Password — the account password.
Snowflake Key-Pair (RSA JWT) Authenticates using an RSA private key to generate a signed JWT for Snowflake-secured endpoints. Provide the RSA private key associated with your Snowflake user account.

The Verify SSL Certificates toggle is available for all authentication methods. When enabled (default), the connector validates SSL/TLS certificates on all configured endpoints. Disable this only in controlled environments where endpoints use self-signed certificates.