# Connecting SailPoint and Delinea Secret Server On-Premise To connect SailPoint with Delinea Secret Server, 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. > [!IMPORTANT] > > By default, the provisioning feature is **disabled**, and the connector only supports read-only operations. To support provisioning operations, you must manually enable the feature in the source configuration. **To configure a new source:** 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 **Configure**. 5. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters. 6. 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. 7. 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](). 8. Under **Connection Type**, select **Direct Connection** or **Flat File**. - **Direct Connection** - A direct connection fetches data from the **Virtual Appliance Cluster** you choose as the application connector for the source. A direct connection configuration allows for real-time updates. For more information about configuring and deploying virtual appliances, refer to the [Virtual Appliance Reference Guide](). - **Flat File** - Select the flat file if no connector is available, or if another system restricts the connection. This option allows only reading and aggregating data as a generic/delimited application. Provisioning activity is unsupported, and additional configuration pages like connection settings and aggregation settings are unavailable. 9. If you selected **Direct Connection**, in **Virtual Appliance Cluster**, select the virtual appliance cluster that will be used as the application connector for the source. 10. (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](). 11. 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](). 12. 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. In the **Virtual Appliance Cluster** dropdown list, select the virtual appliance to use when communicating with your organization's systems. For more information, refer to [SailPoint Virtual Appliances](). 4. (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](). 5. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 6. (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](). 7. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default. - **Enable Provisioning** - Set the toggle to **Enabled** to allow the source to create, update, and deactivate accounts in the connected source system. - **Disable Provisioning** - Set the toggle to **Disabled** to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source. 8. Select **Save**. ## Connection Settings Configure a secure, direct connection to the source. > [!NOTE] > > **Screenshot** > > [![Delinea connection settings with Connection Timeout, Host URL, and API Token fields]()]() 1. Set the **Connection Timeout** in minutes. This sets the maximum duration of time allowed for the connector to establish a connection to the source. If the connector can't establish a connection before the duration expires, the connection fails. 2. Enter the **Host URL** of the Delinea SCIM server source. 3. Enter the **API Token** provided by the source for authentication. > **Note** > > The Delinea Secret Server On-Premise connector only supports OAuth 2.0 authentication with API tokens. 4. Select **Save**. ## Aggregation Settings Configure the settings for your aggregation. You can configure the page size, account filters, group filters, role filters, and you can provide JSON paths for schema attributes. > [!NOTE] > > **Screenshot** > > [![Delinea aggregation settings with Page Size, filters, and JSON Path Attribute Mapping]()]() 1. Enter your desired **Page Size**. The page size sets the number of records to aggregate in a single page when iterating over large datasets. The default is 50 records per page. 2. Enter the **Account Filter**, **Group Filter**, and **Roles Filter** conditions to help ensure your aggregation process only handles the correct accounts or groups. For example: `userName sw "S"` or `displayName sw "S"` 3. (Optional) To aggregate any additional attributes during the aggregation operation specify the attribute name and its corresponding JSON path in the **JSON Path Attribute Mapping** section. A matching schema attribute must be added to the Account Schema for any JSON path you add. The connector can't create additional attributes in the Account Schema as part of this process. > **Note** > > Additional attributes are not supported. Enter the **Attribute Name** and its associated **JSON Path**. - Select **Add Another** to add another attribute to the list. - Select the **Delete** icon ![]() to remove an attribute from the list. 4. 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.