Skip to content

Integrating SailPoint with Exasol

Exasol is a high-performance, in-memory, relational database management system designed specifically for analytics, business intelligence, and data warehousing. Built on a massively parallel processing (MPP) architecture and featuring columnar storage, Exasol scales efficiently to deliver ultra-fast query execution over massive datasets. This document provides instructions to configure a new direct connection to an Exasol source. For a reference to the terminology specific to SailPoint products, refer to Source and Connector Definitions.

Note

To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the SaaS Release Notes page.

Supported Features

The Exasol connector supports the following:

Account Management

  • Aggregate Users

Entitlement Management

  • Aggregate Databases

Important

Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:

  • Organization Admins: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
  • Regular Users: Limited to 1 manual account or entitlement aggregation per day per source.

These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

Prerequisites

Ensure the following prerequisites are met before proceeding with the configuration:

  • You have the Account ID and Personal Access Token to perform the operations. To obtain the Account ID and Personal Access Token, complete the following steps:

    1. Go to Profile.
    2. Copy the Account ID.
    3. Generate a Personal Access Token with read access for users and databases.

  • For more information about Personal Access Tokens, refer to the Exasol Personal Access Token documentation.

Note

The linked document is not maintained by SailPoint and is subject to change without notice.

Required Permissions

  • The user must have the Owner role.
  • The Personal Access Token must include at least the Users: Read and Database: Use scopes.