# SailPoint Doppler Connector Documentation

> Doppler Connector Documentation

# Documentation

# Connecting SailPoint and Doppler

To connect SailPoint to the source, perform the following tasks:

## Adding and Configuring the Source in SailPoint

To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs.

1. Go to **Admin \> Connections \> Sources**.
2. Select **Create New**.
3. Search for a source type and select **Actions**.
4. In the **Actions** dropdown, select the setup method:

   - **Express Setup** - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started.

     > **Note**
     >
     > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>). For more information, contact your SailPoint Customer Service Manager.
   - **Standard Setup** - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

### Express Setup

1. Review the directions and select **Start Express Setup**.
2. Review the pre-populated source name, source owner, and description. To update, select **Edit**.

   > **Note**
   >
   > Source name must be unique.
3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider.

   > **Note**
   >
   > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>).
4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** page.
5. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation.

   - If you want to aggregate now, select **Aggregate**.

     - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**.
     - To see the list of aggregated source accounts, go to **Account Management \> Accounts**.
   - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet.

### Standard Setup

Configure more detailed settings relative to Express Setup.

1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters.
3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](<https://documentation.sailpoint.com/saas/help/sources/index.html#assigning-a-source-owner>).
4. (Optional) Select a governance group to grant its members [source](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#source-sub-admin-user-level>) or [role](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#role-sub-admin-user-level>) sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html>).
5. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](<https://documentation.sailpoint.com/saas/help/setup/identity_profiles.html>).
6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Here, continue to configure your connected source.

## Base Configuration

Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary.

1. Enter a descriptive **Source Name** for the connection.
2. Enter the **Source Description** that provides details necessary to distinguish it from similar connection sources.
3. In **Source Owner**, begin typing the name of the source owner.
4. (Optional) Select the appropriate **Governance Group for Source Management** from the dropdown list. For more information about governance groups, refer to [Associating Governance Groups with a Source](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html#associating-a-governance-group-with-a-source>).
5. Select **Create Manual Work Items** to enable the source to support additional source management features such as creating accounts and access profile management.

   > **Important**
   >
   > Once you enable this feature, it can't be disabled.

   For more information on manual work items, refer to [Work Items](<https://developer.sailpoint.com/docs/api/work-items>). For more information on SailPoint features, refer to [SailPoint Identity Services](<https://documentation.sailpoint.com/saas/help/index.html>).
6. Select **Save**.

## Connection Settings

Configure a secured, direct connection to the source.

1. Enter the Doppler API base endpoint as **Base URL**. For example, `https://api.doppler.com/v3`.
2. Enter the **API Token**. This connector uses this token as a Bearer token to authenticate connector requests.
3. Select **Save**.

## Review and Test

Perform a test to confirm the connection to SailPoint.

1. Go to **Review and Test**.
2. Confirm that the entries in each field are correct.

   If you note any mistakes, return to the section and make corrections.
3. Select **Test Connection**.

## SailPoint Application Onboarding

SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface.

For more information, refer to [Application Onboarding](<https://documentation.sailpoint.com/saas/help/ai/app_onboarding/index.html>) in the SailPoint SaaS documentation.

# Integrating SailPoint with Doppler

Doppler is a secrets management platform that helps teams manage application configuration and secrets across development, staging, and production environments. It provides workplace-level team management, project-based access controls, secrets versioning, and a REST API for programmatic administration. This document provides the instructions required to configure a new direct connection between SailPoint and Doppler. For a reference to the terminology specific to SailPoint products, refer to [Source and Connector Definitions](<https://documentation.sailpoint.com/saas/help/sources/index.html#source-and-connector-definitions>).

> [!NOTE]
>
> To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes](<https://community.sailpoint.com/release-notes/saas>) page.

## Supported Features

The Doppler connector supports the following:

### Account Management

- Aggregate Workplace Users

### Entitlement Management

- Aggregate Workplace Roles

> [!NOTE]
>
> This connector is read-only. It supports account and entitlement aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported in this release.

> [!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

Before configuring the Doppler connector, ensure you have the required API access from a Doppler workplace with appropriate permissions.

1. Sign in to the [Doppler Dashboard](<https://dashboard.doppler.com>) with a **Workplace Owner** or **Workplace Admin** account.
2. Go to **Tokens \> Personal**.
3. Generate a new API token and copy it immediately. Doppler tokens are high-entropy secrets and may not be displayed again after creation.
4. Store the token securely.
5. Record the following values for SailPoint configuration:

   - **Base URL**
   - **API Token**

> [!NOTE]
>
> The API token authenticates all connector requests via the `Authorization: Bearer <TOKEN>` header. The token is scoped to the workplace associated with the account that created it. A workplace identifier is not required as a separate connection parameter - the workplace context is implicit in the token.

## Required Permissions

### Who Can Generate Tokens

Any Doppler user can generate a **Personal Token** or **CLI Token** for their own account. For governance aggregation, use a token created by a user with sufficient workplace visibility.

| Token Type | Access Scope | Recommended Use |
| --- | --- | --- |
| **Personal Token** | Read/write access to all resources on the account | Full aggregation of users and workplace roles |
| **Audit Token** | Read-only access to users and groups | Limited read-only aggregation (may not cover all role endpoints) |

### Workplace Permissions

To aggregate workplace users and roles, the token owner should hold a workplace role with visibility into team settings:

- **Owner** - Full workplace access; can view all users and roles.
- **Admin** - Full project access; can view team settings.
- **Collaborator** - Limited; may not have sufficient permissions to list all workplace users or roles.

**Recommendation:** Use a Personal Token created by a **Workplace Owner** or **Workplace Admin** account to ensure reliable access to system endpoints.

## Key Implementation Notes

- **Workplace roles are the primary entitlement model** exposed by this connector at the account level. Doppler provides three built-in workplace roles: owner, admin, and collaborator.
- User attribute include **Identifier** and **Slug**. **Identifier** is the account identity attribute required by the Doppler API (`$.id`) to retrieve an individual user. **Slug** is consistent across workplaces. **Identifier** is unique per workplace membership.
- Account correlation uses **Email**.
- **Tokens are workplace level**, so generate separate token for each workplace.
- **API rate limits** apply per plan and per token. If aggregation fails with HTTP 429, review Doppler's rate limit headers and adjust aggregation schedules accordingly.

## References

For more information refer to the following resources:

- [Doppler Documentation](<https://docs.doppler.com/docs/start>)
- [Doppler API Reference](<https://docs.doppler.com/reference/api>)

> [!NOTE]
>
> The linked document is not maintained by SailPoint and is subject to change without notice.

# Schema Reference

The application schema is used to configure the objects returned from a connector.

> [!NOTE]
>
> - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.
> - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified.

The Doppler connector uses the following default correlation and object configurations.

## Default Account Schema

Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.

The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.

### Default Account ID

SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as *account IDs*.

> [!CAUTION]
>
> Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.
>
> To resolve issues caused by changing account IDs, reconfigure them to their default values.

The following table lists the default account IDs for this connector:

| Account ID | Schema Object Type |
| --- | --- |
| Identifier | Account |

### Default Account Attributes

The Doppler connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.

| Attribute Name | Description |
| --- | --- |
|  |  |

| Identifier | Unique UUID of the user in the current workplace, different for different workplace | | Role | Workplace role assigned to the user (for example, owner, admin, collaborator) | | Created at | Timestamp when the user was added to the workplace | | Kind | Member type of the account (for example, user) | | Slug | Slug of the user, same across all workplaces the user is a member | | Email | Email address of the user | | Name | Display name of the user | | Username | Username handle for the user | | MFA Enabled | Indicates whether OTP or security-key MFA is enabled on the account | | Third Party SSO Enabled | Indicated whether the user signs in via third-party SSO (for example, Google or Okta) | | SAML SSO Enabled | Indicated whether the user signs in via workplace SAML SSO |

> [!NOTE]
>
> A user's `Slug` remains the same across all workplaces the user belongs to, while the `Identifier` attribute changes for each workplace. `Identifier` is the account identity attribute because retrieving an individual user from the Doppler API requires the Identifier (`$.id`), not the `Slug`.

## Default Entitlement Attributes

Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to [Managing Entitlements](<https://documentation.sailpoint.com/saas/help/access/entitlements.html>) for more information.

> [!CAUTION]
>
> Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations.

| Attribute Name | Description |
| --- | --- |
| Name | Display name of the workplace role (for example, Owner, Admin, Collaborator) |
| Identifier | Unique identifier of the workplace role (for example, owner, admin, collaborator) |
| Created At | Timestamp when the workplace role was created |
| Is Custom Role | True if the role is a custom role created in the workplace; false for built-in roles |
| Is Inline Role | True if permissions were manually selected at assignment time rather than from a named role |
| Permissions | Workplace permission slugs granted by this role (for example, team, logs, billing, settings) |

> [!NOTE]
>
> Doppler provides three built-in workplace roles - **Collaborator**, **Admin**, and **Owner**. Custom workplace roles are available on Team and Enterprise plans. Built-in roles cannot be deleted; custom roles can be created and managed from **Team \> Roles** in the Doppler Dashboard.