# SailPoint Harness Connector > Harness Connector Documentation # Documentation # Connecting SailPoint and Harness To connect SailPoint with Harness, perform the following tasks: ## Adding 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. Sign in to SailPoint. 2. Go to **Admin \> Connections \> Sources**. 3. Select **Create New**. 4. Search for the connector by entering the name in the search box, and then select **Actions**. 5. In the **Actions** dropdown list, select the setup method: - [**Express Setup**](<#configuring-a-source-using-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](). For more information, contact your SailPoint Customer Service Manager. - [**Standard Setup**](<#configuring-a-source-using-standard-setup>) - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup. ### Configuring a Source Using Express Setup Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data. 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** > > The source name must be unique. You can change these settings later in the source configuration. 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](). 4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** section. 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. ### Configuring a Source Using Standard Setup Use Standard Setup to configure the connector for full feature support. 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](). 4. (Optional) Select a governance group to grant its members [source]() or [role]() sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](). 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](). 6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Continue to configure your connected source there. ## 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 unique name and description for the source. 2. In the **Source Owner** dropdown list, select the identity that owns this source. - To find a source owner, begin entering their name. 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, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 4. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 5. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to [Associating Governance Groups with a Source](). 6. (Optional) Select **Create Manual Work Items** to allow the connector to create manual work items for certain operations. You can also enable this option so the source supports additional source management features such as creating accounts and access profile management. > **Important** > > Once you enable this feature, you cannot disable it. For more information on manual work items in SailPoint, refer to [Work Items](). For more information on SailPoint features, refer to [SailPoint Identity Services](). 7. Select **Save**. ## Connection Settings Provide the values that SailPoint uses to connect to Harness. > [!NOTE] > > **Screenshot** > > [![Connection Settings page with the Harness URL, Account Identifier, and API key fields]()]() 1. In **Harness URL**, enter the HTTPS base URL for the Harness platform host. Do not add `/ng/api` or another path. For example, enter `https://app.harness.io`. 2. In **Account Identifier**, enter the Harness account ID. 3. In **API key**, enter a personal access token or service account token. 4. Select **Save**. ## Aggregation Settings Use an organization filter to control which Harness organizations the connector includes in entitlement and dataset aggregation. > [!NOTE] > > **Screenshot** > > [![Aggregation Settings page with the Organization Filter field]()]() 1. Save a valid **Harness URL**, **Account Identifier**, and **API key** in [Connection Settings](<#connection-settings>). 2. Select **Test Connection**, or select **Refresh** from the **Organization Filter** dropdown list, to load the organization list. 3. In **Organization Filter**, select one or more organizations to include. Leave the selection empty to include every organization that the API key can access. 4. Select **Save**. ## Advanced Settings > [!NOTE] > > **Screenshot** > > [![Advanced Settings page with the Connection Timeout (Minutes) and Page Size fields]()]() 1. In **Connection Timeout (Minutes)**, enter the number of minutes the connector waits during inactivity before it ends the connection. The default is `1`. 2. In **Page Size**, enter the number of records the connector aggregates on each page. Enter a value from `1` through `100`. The default is `50`. 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]() in the SailPoint SaaS documentation. # Dataset Management Dataset Management lets you review the object types a source collects and control how the source aggregates those objects into SailPoint. Use Dataset Management to view and manage resource attributes, datasets and their resources, enable dataset aggregation schedules, perform manual aggregation, and view aggregation history. > [!NOTE] > > Datasets are also available in SailPoint Agentic Fabric. Contact your Customer Success team and refer to [SailPoint Agentic Fabric]() for more information. For more information, refer to [Managing Datasets and Resources]() for datasets, resources, owner correlation, and aggregation. ## Datasets A *dataset* is a named group of one or more related resources that the source aggregates together. When aggregation runs for a dataset, the source collects all resources in that dataset from the managed system in one aggregation job. Activate or deactivate aggregation at the dataset level, not for individual resources. > [!NOTE] > > Each resource belongs to exactly one dataset for that source. The source defines which resources belong to each dataset. You can enable aggregation and review associated resources, but you cannot create or delete datasets or move resources between them. ### Dataset Aggregation Configure aggregation on the **Dataset Aggregations** tab for each dataset. Configure each dataset separately. During aggregation, your owner correlation rules are automatically applied to link machine identities to their human owners. For more information, refer to [Configuring Dataset Aggregations](). ## Resources A resource defines an object type from the managed system. It specifies the kind of object, the attributes the source collects, and how the source identifies and displays each object. Resources form the building blocks of the data model. In the UI, each resource appears under **Dataset Management** \> **Resources** with its schema. A resource does not run aggregation by itself. The dataset that owns the resource collects it during aggregation. For more information, refer to [Managing Resources](). ### Owner Correlation Configure owner correlation on each resource to link aggregated objects to human owners. If you do not configure owner correlation, or if the mapping produces no match, an owner is not assigned. For more information, refer to [Configuring Owner Correlation](). ## Supported Datasets Go to **Dataset Management \> Datasets** on your Harness source to view the datasets the connector aggregates. Select a dataset to review its associated resources and configure aggregation. > [!NOTE] > > Configure aggregation for each dataset separately. For more information, refer to [Dataset Aggregation](). | Dataset Name | Associated Resources | Dataset ID | Default Schedule | | --- | --- | --- | --- | | Service Accounts | Service Account | `service-account` | 2:00 AM UTC daily | | Tokens | API Token, Delegate Token | `token` | 2:00 AM UTC daily | ## Supported Resources Resource schemas appear under **Dataset Management \> Resources**. Connector-specific attributes are read-only. For more information, refer to [Managing Resources](). > [!NOTE] > > When you enable dataset aggregation for a selected dataset, all resources in that dataset are collected at once. Activate or deactivate aggregation at the dataset level, not for individual resources. | Resource Name | Resource Type | Resource ID | | --- | --- | --- | | [Service Account](<#service-account-attributes>) | Account | `harness:service-account` | | [API Token](<#api-token-attributes>) | Credential | `harness:api-token` | | [Delegate Token](<#delegate-token-attributes>) | Credential | `harness:delegate-token` | ### Service Account Attributes Schema attributes for the **Service Account** resource (`harness:service-account`). The identity attribute is `identity`, and the display attribute is `name`. | Attribute Name | Description | Type | Multi-Valued | | --- | --- | --- | --- | | `accountIdentifier` | The Harness account the service account belongs to. | string | No | | `classification` | Account classification. Harness service accounts are machine accounts. | string | No | | `description` | Description of the service account purpose. | string | No | | `email` | Email address associated with the service account. | string | No | | `identifier` | Unique identifier of the service account within its scope. | string | No | | `identity` | Scoped unique identity of the service account. | string | No | | `name` | Display name of the service account. | string | No | | `orgIdentifier` | The organization the service account is scoped to, if any. | string | No | | `projectIdentifier` | The project the service account is scoped to, if any. | string | No | | `roles` | Role identifiers assigned to the service account through role assignments. | string | Yes | | `tags` | Key-value tags applied to the service account (JSON value). | string | No | ### API Token Attributes Schema attributes for the **API Token** resource (`harness:api-token`). The identity attribute is `identity`, and the display attribute is `name`. | Attribute Name | Description | Type | Multi-Valued | | --- | --- | --- | --- | | `accountIdentifier` | The Harness account the token belongs to. | string | No | | `apiKeyIdentifier` | Identifier of the parent API key grouping the token belongs to. | string | No | | `apiKeyType` | Indicates whether the token is a personal access token (USER) or service account token (SERVICE\_ACCOUNT). | string | No | | `createdAt` | Date and time of token creation in ISO-8601 UTC format, for example `2026-03-30T02:30:00Z`. | string | No | | `expiryAt` | Date and time of token expiry in ISO-8601 UTC format, for example `2026-03-30T02:30:00Z`. | string | No | | `identifier` | Unique identifier of the token. | string | No | | `identity` | Scoped unique identity composed of parent identifier and token identifier. | string | No | | `lastModifiedAt` | Date and time of the last modification in ISO-8601 UTC format, for example `2026-03-30T02:30:00Z`. | string | No | | `name` | Display name of the token. | string | No | | `owner` | Owner of the token. Personal access tokens (USER) use the owning user identifier. Service account tokens (SERVICE\_ACCOUNT) use the service account identifier. | string | No | | `parentIdentifier` | Identifier of the owning user or service account. | string | No | | `valid` | Indicates whether the token is currently valid. | boolean | No | | `validFrom` | Date and time from which the token is valid in ISO-8601 UTC format, for example `2026-03-30T02:30:00Z`. | string | No | | `validTo` | Date and time after which the token expires in ISO-8601 UTC format, for example `2026-03-30T02:30:00Z`. | string | No | ### Delegate Token Attributes Schema attributes for the **Delegate Token** resource (`harness:delegate-token`). The identity attribute is `identity`, and the display attribute is `name`. | Attribute Name | Description | Type | Multi-Valued | | --- | --- | --- | --- | | `createdAt` | Date and time of token creation in ISO-8601 UTC format, for example `2026-03-30T02:30:00Z`. | string | No | | `createdBy` | Creator of the delegate token. Uses the next-gen user unique ID when available. Otherwise stores the creator details as JSON. | string | No | | `identity` | Unique identity of the delegate token. This value matches `uuid`. | string | No | | `name` | Display name of the delegate token. | string | No | | `owner` | Human owner of the delegate token. Uses the next-gen user unique ID when available. Otherwise uses the creator UUID. | string | No | | `ownerIdentifier` | Organization or project identifier that owns the delegate token, if scoped. | string | No | | `parentUniqueId` | Harness unique ID of the account, organization, or project that owns the delegate token. | string | No | | `status` | Lifecycle status of the delegate token. | string | No | | `uuid` | Unique identifier of the delegate token. | string | No | # Integrating SailPoint with Harness Harness is a continuous integration and continuous delivery (CI/CD) platform. Use the Harness SaaS connector to aggregate Harness users as accounts and user groups and roles as entitlements. The connector also aggregates service accounts as machine identities. It aggregates API tokens and delegate tokens as credentials. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features | Feature | Description | | --- | --- | | Test connection | Validates the Harness URL, account identifier, and API key. | | Account aggregation | Aggregates Harness users as SailPoint accounts. | | Entitlement aggregation | Aggregates Harness user groups and roles as entitlements. | | Dataset aggregation | Aggregates Harness service accounts, API tokens, and delegate tokens. | ### Non-Human Identity Discovery - Aggregate Harness service accounts, API tokens, and delegate tokens Refer to Dataset Management for more information. Refer to [Discovering Potential Non-Human Accounts]() for more information. ## Prerequisites Complete the following tasks before you configure the Harness SaaS source: 1. Ensure that SailPoint can reach your Harness account over HTTPS. 2. Copy the Harness account identifier. 3. Create a Harness personal access token or service account token. 4. Grant the token's principal **View** permission for users, user groups, roles, service accounts, and delegates. For more information about Harness API keys, refer to [Create and Manage Harness API Keys](). > [!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]() for more information. > - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified. The Harness connector uses the following default correlation and object configurations. ## Default Correlation Configuration Before you aggregate accounts from this source, you can map account attributes with their corresponding identity attributes based on your requirements. You can customize the correlation configuration. Refer to [Assigning Source Accounts to Identities]() for more information. When you first create the Harness source, the default correlation mapping is: | Account Attribute | Operation | Identity Attribute | | --- | --- | --- | | email | Equals, ignoring case | Email | ## 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]() for more information. ### Default Account Attributes The Harness connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified. The account schema represents Harness users. The identity attribute is `uuid`, the display attribute is `name`, and the group attribute is `group`. | Attribute Name | Description | | --- | --- | | `uuid` | Unique identifier generated by Harness for the user. | | `name` | The user's display name. | | `email` | The user's email address. | | `locked` | Indicates whether the user account is locked. | | `disabled` | Indicates whether the user account is disabled. | | `externallyManaged` | Indicates whether the user is managed by an external identity provider, for example SSO or SCIM. | | `twoFactorAuthenticationEnabled` | Indicates whether the user enabled two-factor authentication. | | `group` | User group identifiers for the user, including inherited groups. | | `role` | Role identifiers assigned to the user through role assignments. | ## 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]() 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. ### Default Group Attributes The Harness connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups. The group entitlement represents a Harness user group. The identity attribute is `identifier`, and the display attribute is `name`. | Attribute Name | Description | | --- | --- | | `identifier` | Unique identifier of the user group. | | `name` | Display name of the user group. | | `description` | Description of the user group purpose. | | `accountIdentifier` | The Harness account the group belongs to. | | `orgIdentifier` | The organization the group is scoped to, if any. | | `projectIdentifier` | The project the group is scoped to, if any. | | `externallyManaged` | Indicates whether an external identity provider manages the group. | | `harnessManaged` | Indicates whether Harness manages the group. | | `ssoLinked` | Indicates whether the group links to an SSO provider. | ### Default Role Attributes The Harness connector supports roles. The following attributes must be configured on the managed system and in the SailPoint source schema to manage roles. The role entitlement represents a Harness role. The identity attribute is `identifier`, and the display attribute is `name`. | Attribute Name | Description | | --- | --- | | `identifier` | Unique identifier of the role. | | `name` | Display name of the role. | | `description` | Description of the role. | | `scopeLevel` | The scope level the role applies to: account, org, or project. | | `harnessManaged` | Indicates whether the role is a built-in Harness-managed role or a custom role. | | `permissions` | Permission identifiers granted by the role. | | `roleAssignedToUserCount` | Number of users assigned to the role. | | `roleAssignedToUserGroupCount` | Number of user groups assigned to the role. | | `roleAssignedToServiceAccountCount` | Number of service accounts assigned to the role. | # Troubleshooting If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support. For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information: - [SailPoint Identity Services Documentation]() - [SailPoint Support Knowledge Base]() - [SailPoint Developer Community]() ## Debug Logs For information about managing additional source settings, including debug logging and downloading connector logs, refer to [Managing Additional Settings]().