Skip to content

Integrating SailPoint with Enclave

Enclave is a network connectivity platform that lets organisations build private overlay networks between hosts, services, and people. Administrators manage organisations, systems, enrolment keys, and users from the Enclave Portal, and the same operations are exposed via the Enclave REST API. This document provides instructions to configure a new direct connection to an Enclave 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 Enclave connector supports the following:

Account Management

  • Aggregate Accounts (Users)

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:

  • An Enclave account with access to the target organization. The user creating the API token must be able to view the organization’s user list in the Enclave Portal.
  • Supported authentication type: Personal Access Token (PAT) authentication.
  • The PAT is created from the user’s account page in the Enclave Portal.
  • An Organization ID is required to fetch organization accounts from Enclave. For more information about token generation, refer to the Enclave API documentation.

Required Permissions

  • API credentials in Enclave are Personal Access Tokens (PATs) created from a user’s account page in the Enclave Portal.
  • There is no separate “service account” object. It is recommended to provision a dedicated Enclave user (for example, an automation/service identity) and use that user’s PAT rather than a human’s personal token.
  • Per the Enclave documentation, “Created tokens currently have access to all of the Enclave organizations that your account has access to in the portal.” The owning user must therefore have access to the specific organization whose users you intend to aggregate.
  • An Organization ID for the target organization is required.
  • For more information about authentication and organization IDs, refer to the following resources:

Note

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