# SailPoint Delinea Secret Server On-Premise Connector Documentation > Delinea Secret Server On-Premise Connector Documentation # Documentation # 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. # Integrating SailPoint with Delinea Secret Server On-Premise > [!NOTE] > > **Integration** > > This is an integration and requires additional licensing or subscriptions to utilize it. For more information, contact your customer success manager. The SailPoint connector for Delinea Secret Server On-Premise provides deep governance for Accounts and Groups (Safes). This integration is capable of end-to-end life cycle management. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features The Delinea Secret Server On-Premise source supports user (account) and entitlement (group and roles) management. ### User Management (Accounts) - Aggregation of internal and external users - Refresh users - Create user provisioning for local users - Enable / Disable users with provisioning - Add users to groups > **Note** > > The Delinea Secret Server On-Premise connector uses the PATCH method to add and remove users in groups via the group endpoints. - Remove users from groups - Update a user's Email ID (`emails.work.primary.value`) and Username (`userName`) attributes using the `/users` endpoint. - Assign roles to users > **Note** > > The Delinea Secret Server On-Premise connector uses the PATCH method to assign roles to users, remove roles from users, fetch roles, and fetch users assigned to roles via the users' endpoints. - Remove roles from users ### Group Management (Entitlements) - Group aggregation - Single user aggregation - Aggregate container permissions as direct permissions - Roles aggregation - Single role aggregation ### Supported Use Cases The following use cases are facilitated by the Delinea Secret Server On-Premise connector. **Read Operation** - Fetch local and external users from the PAM system. - Fetch local groups from the PAM system. - View Safes / Containers and view how their permissions are assigned to groups. - Fetch roles from the PAM system. **Provisioning** - Create local users on the PAM system. - Add or remove internal and external users from local groups. This indirectly assigns and revokes Safes and their associated permissions. - Enable or disable internal and external users residing on the PAM system. - Assign roles to users, and remove roles from users. For more information on features, refer to [Source Features](). ## Prerequisites Complete the following necessary tasks before configuring SailPoint Delinea Secret Server On-Premise connector. > [!CAUTION] > > The Delinea Secret Server On-Premise documentation referenced in this page is not managed by SailPoint, and is subject to change without notice. - Configure at least one virtual appliance cluster and successfully test the connection. For instructions, refer to the [Virtual Appliance Reference Guide](). - Configure a SCIM connector for Delinea Secret Server. For more information, refer to [SCIM Connector for Secret Server]() in the Delinea Secret Server documentation. - Configure an Application User account. For more information, refer to [Account Permissions]() in the Delinea Secret Server documentation. - Generate a token for authorization. For more information, refer to [SCIM Connector Endpoint Information]() in the Delinea Secret Server documentation. - The Delinea Secret Server On-Premise connector requires Delinea SCIM Connector version 4.4.4 or later to assign roles to users, remove roles from users, fetch roles, and fetch users assigned to roles. ## Required Permissions for Managing Roles Specific permissions must be set in the source to enable SailPoint to manage roles. The following table lists the features that rely on which required permissions found in the Delinea Secret Server source. | Feature | Required Permission | Description | | --- | --- | --- | | Fetch roles | View Roles | Allows a user to view roles in the system. Also allows a user to see which groups are assigned to which roles. | | View the roles assigned to a user or a group | View Group Roles | Allows a user to see which groups and users are assigned to which roles. Does not allow a user to change these assignments. | | Edit the roles assigned to a user | Administer Role Assignment | Allows a user to view which users and groups are assigned to which roles. Also allows users to assign users and groups to different roles. | ## Supported Managed Systems The Delinea Secret Server On-Premise source supports the following managed systems: - Delinea SCIM Connector (On-Premise) 4.4.4 > **Note** > > This managed system is required to manage roles. - Delinea SCIM Connector (On-Premise) 4.6.0 - Delinea SCIM Connector (On-Premise) 4.7.0 # Provisioning When SailPoint provisions new accounts to a connected Delinea Secret Server On-Premise source, it uses the attributes on the **Create Profile** tab as a template for what to configure for each new account. The information on the **Create Profile** can also be referred to as the provisioning policy. > [!IMPORTANT] > > This topic describes the configuration of the default Create Profile. However, SailPoint recommends that you work with Services to define a Create Profile specific to your needs. The following provisioning attributes create the required information for a new Delinea Secret Server On-Premise account. You may need to edit the final values. ## Default Create Account Attributes | Attribute | Description | | --- | --- | | emails.work.primary.value | The user's work email address. Disabled by default. | | userName | Create Unique Account ID. The user's username within the Delinea Secret Server system. Sets the `id` SailPoint Account attribute. | | active | The user's active status in the Delinea Secret Server system. Static value. Default static value is `true`. | | password | The user's authentication password within the Delinea Secret Server system. Static value. Default static value is null. | # 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 Delinea Secret Server On-Premise 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]() 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 | | --- | --- | | id | Account | | id | Group | | id | Roles | > [!NOTE] > > Account IDs might also be referred to as "Native IDs". ### Default Account Attributes The account schema for the Delinea Secret Server On-Premise connector contains the following attributes related to Users within the source. > [!NOTE] > > The Delinea On-Premise Connector only supports attributes supported by the Delinea SCIM server. | Attribute Name | Description | | --- | --- | | id | The user's unique identifier | | userName | The user's username | | emails.work.primary.value | The user's organization | | groups | The list of groups to which the user belongs | | displayName | The user's display name | | active | The user's active status in the Delinea Secret Server On-Premise system | | roles | A list of roles assigned to the user | | meta.created | Timestamp for the user's creation | | meta.lastModified | Timestamp for the user's most recent modification | | meta.location | URL to access the SCIM resource | | LinkedObject.source | The name of the external application in which an account object is saved. If this is a PAM local object, the value is `null`. | | LinkedObject.nativeIdentifier | An account object's unique identifier within its external application. For example, this can be the LDAP DN. If this is a PAM local object, the value is `null`. | ## 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 Delinea Secret Server On-Premise connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups. > [!NOTE] > > The Delinea On-Premise Connector only supports attributes supported by the Delinea SCIM server. | Attribute Name | Description | | --- | --- | | id | The group's unique identifier | | displayName | The group's display name | | members.value | A list of the group's members | | meta.created | Timestamp for the group's creation | | meta.lastModified | Timestamp for the group's most recent modification | | meta.location | URL to access the SCIM resource | | Group.source | The name of the external application in which a group object is saved. If this is a PAM local object, the value is `null`. | | Group.nativeIdentifier | A group object's unique identifier within its external application. For example, this can be the LDAP DN. If this is a PAM local object, the value is `null`. | ### Default Roles Attributes The Delinea Secret Server On-Premise connector supports roles. The following attributes must be configured on the managed system and in the SailPoint source schema to manage roles. > [!IMPORTANT] > > If you updated an existing source to support role management, refer to [Add the Roles Support to Existing Sources](<#add-the-roles-support-to-existing-sources>) to add the Roles schema to your source. | Attribute Name | Description | | --- | --- | | id | Unique identifier for the role | | display | The name displayed for the role | | value | The role's value | | meta.created | Timestamp for the role's initial creation | | meta.lastModified | Timestamp for the role's most recent modification | | meta.location | URL to access the SCIM resource | #### Add the Roles Support to Existing Sources If you have an existing source you've updated to support role management, you need to manually add the Roles schema and update the Accounts schema. Sources created following the update include the Roles schema and the updated Account schema by default. To add roles management support to an existing source: 1. Use the **createSchema** API to create a new Group Schema for your source. This new schema will become the Roles schema. For more information, refer to [Create Schema on a Source](). Use the following request: ```json "nativeObjectType": "roles", "identityAttribute": "id", "name": "roles", "displayAttribute": "display", "hierarchyAttribute": null, "includePermissions": false, "features": [ "PROVISIONING" ], "configuration": {}, "attributes": [ { "name": "id", "type": "STRING", "schema": null, "description": "Unique identifier for the Role", "isMulti": false, "isEntitlement": false, "isGroup": false }, { "name": "display", "type": "STRING", "schema": null, "description": "Displayable Name of the Role", "isMulti": false, "isEntitlement": false, "isGroup": false }, { "name": "value", "type": "STRING", "schema": null, "description": "The value of a Role", "isMulti": false, "isEntitlement": false, "isGroup": false }, { "name": "meta.created", "type": "STRING", "schema": null, "description": "Resource creation date and time", "isMulti": false, "isEntitlement": false, "isGroup": false }, { "name": "meta.lastModified", "type": "STRING", "schema": null, "description": "Last modified date and time", "isMulti": false, "isEntitlement": false, "isGroup": false }, { "name": "meta.location", "type": "STRING", "schema": null, "description": "URL to access SCIM resource", "isMulti": false, "isEntitlement": false, "isGroup": false } ] } ``` 2. Update the Account schema with the new Roles schema. a. Get the Account schema using the **getSchema** API. For more information, refer to [Get Source Schema by ID](). b. Copy the schema to a file and add the following JSON to the new schema to add roles to the Account schema. Replace the placeholder `id` value in the following example payload with the `id` value from the new schema. ```json { "name": "roles", "type": "STRING", "schema": { "type": "CONNECTOR_SCHEMA", "id": "", "name": "roles" }, "description": "A list of roles assigned to the user", "isMulti": true, "isEntitlement": true, "isGroup": true } ``` c. Use the JSON you created as the payload to update the Account schema in the source using the **replaceSchema** API. For more information, refer to [Update Source Schema (Full)](). # Enable Connector Logging This topic provides the steps needed to enable logging on SailPoint using REST APIs. > [!NOTE] > > This topic only applies to VA-based integrations. > [!NOTE] > > The examples provided might not match your configuration. Use the logging levels and logging classes reference at the bottom of the topic to configure your API responses to match your connector. This process is broken up into four steps: 1. Identify the Virtual Appliance (VA) cluster on which you want to enable logging. 2. Get the logging configuration for the existing VA cluster. 3. Update the VA cluster to enable logging levels. 4. Observe logging changes to the logging levels. ### Identify the Virtual Appliance Cluster Select the VA on which you need to enable logging using REST API. If you already know the VA application's `id`, proceed to [Get the Logging Configuration](<#get-the-logging-configuration>). 1. Make the following call to the REST API to return a list of available VA clusters: GET /v3/managed-clusters The REST API returns a response that looks similar to the following: ```json [ { "id": "2c9180866166b5b0016167c32ef31a66", "name": "Development Cluster", "description": "Development Cluster", "clientType": "CCG", "ccgVersion": "373_535_70.2.0", "pinnedConfig": true, "logConfiguration": null }, { "id": "2c9180846a93ce60016ab29f039944de", "name": "Cloud Cluster", "description": "Cloud Cluster", "clientType": "CCG", "ccgVersion": "373_535_70.2.0", "pinnedConfig": true, "logConfiguration": { "clientId": null, "durationMinutes": 60, "expiration": "2020-12-15T19:13:36.079Z", "rootLevel": "DEBUG", "logLevels": { "sailpoint.connector.ADLDAPConnector": "DEBUG" } } } ] ``` > **Note** > > The previous example code shows two VA clusters. One VA cluster has a log configuration and the other does not (refer to the `logConfiguration` value in each returned VA cluster). This is because one of the clusters already has logging enabled. This is just an example configuration, and your environment may not have logging enabled on a cluster. 2. Identify the VA cluster that you want to enable logging on by its name or description and record its `id` attribute. ### Get the Logging Configuration Get your selected VA's cluster logging configuration and identify the values you need to update. 1. Make the following call to the REST API to return the VA cluster's logging configuration. Replace `{id}` with the VA cluster's `id` attribute value recorded earlier. GET /v3/managed-clusters/{id}/log-config - If the VA doesn't have a logging configuration currently set, it returns `204 No Content` as a response. - If the VA has an existing logging configuration, it returns something similar to the following: ```json { "clientId": null, "durationMinutes": 60, "expiration": "2020-12-15T19:13:36.079Z", "rootLevel": "DEBUG", "logLevels": { "sailpoint.connector.ADLDAPConnector": "DEBUG" } } ``` You'll need to configure the following information in the response: - `durationMinutes` is the number of minutes logging should remain enabled. - `rootLevel` is the default level for all logs. For more information, refer to [Logging Levels](<#logging-levels>). - `logLevels` is a map object with logging classes as keys and logging levels as values. - For keys, refer to [Logging Classes](<#logging-classes>) for commonly used logging classes. - For a list of available values, refer to [Logging Levels](<#logging-levels>). ### Update Logging Configuration Update the VA cluster configuration returned by the REST API to update the logging settings as needed. 1. Make the following call to the REST API to update the VA cluster's logging configuration. Replace `{id}` with the VA cluster's `id` attribute value recorded earlier. PUT /v3/managed-clusters/{id}/log-config 2. Submit your configuration changes to the REST API in a JSON body. - If the VA cluster did not already have a logging configuration and you received a `204 No Content` response, you can create a new one. - If the VA returned a configuration, you can edit it to include the changes. The JSON body should be as follows: ```json { "durationMinutes": 60, "rootLevel": "DEBUG", "logLevels": { "sailpoint.connector.ADLDAPConnector": "DEBUG" } } ``` Consider the following as you edit the JSON: - `durationMinutes` is the number of minutes logging should remain enabled. - `rootLevel` is the default level for all logs. For more information, refer to [Logging Levels](<#logging-levels>). - `logLevels` is a map object with logging classes as keys and logging levels as values. - For keys, refer to [Logging Classes](<#logging-classes>) for commonly used logging classes. - For a list of available values, refer to [Logging Levels](<#logging-levels>). If the update was successful, the REST API should return a response similar to the following: ```json { "clientId": null, "durationMinutes": 60, "expiration": "2020-12-15T19:13:36.079Z", "rootLevel": "DEBUG", "logLevels": { "sailpoint.connector.ADLDAPConnector": "DEBUG" } } ``` ### Observe Logging Changes Approximately five minutes after you update the configuration, the VA cluster starts generating log files you can review. You can view the log files in **ccg.log**. ### References The tables in this reference section list information that can be helpful when creating the JSON body you'll use to configure the VA cluster's configuration file. #### Logging Levels | Logging Level | Description | | --- | --- | | ERROR | Designates error events that might still allow the connector to continue. | | WARN | Designates potentially harmful situations. | | INFO | Designates information messages that highlight process at a coarse-grain level. | | DEBUG | Very verbose. Fine grain logging levels used for development and debugging. | | TRACE | Most verbose. Finer grain logging levels than debugging. | #### Logging Classes | Connector | Logging Class | | --- | --- | | Active Directory | sailpoint.connector.ADLDAPConnector sailpoint.connector.LDAPConnector | | AIX | openconnector.connector.unix.AIXConnector openconnector.connector.unix.UnixConnector | | Amazon Web Services | logger.aws.name=openconnector.connector.aws logger.aws.level=trace logger.aws.additivity = false logger.aws.appenderRef.rolling.ref = STDOUT | | Atlassian Suite Cloud | sailpoint.connector.OpenConnectorAdapter openconnector.connector.atlassian.AtlassianConnector | | Atlassian Data Center | sailpoint.connector.OpenConnectorAdapter openconnector.connector.atlassian.AtlassianDataCenterConnector | | Microsoft Entra ID | sailpoint.connector.AzureADConnector | | Box | openconnector.connector.BoxNetConnector sailpoint.connector.OpenConnectorAdapter | | Cerner | openconnector.connector.CernerConnector sailpoint.connector.OpenConnectorAdapter | | Delimited File | logger.DelimitedFileConnector.name = sailpoint.connector.DelimitedFileConnector logger.DelimitedFileConnector.level = debug logger.DelimitedFileConnector.additivity = false logger.DelimitedFileConnector.appenderRef.rolling.ref = STDOUT | | Dropbox | openconnector.connector.DropBoxConnector sailpoint.connector.OpenConnectorAdapter | | Epic | openconnector.connector.EPICConnector sailpoint.connector.OpenConnectorAdapter | | GE Centricity | openconnector.connector.GECentricity sailpoint.connector.OpenConnectorAdapter | | Google Apps / G Suite | openconnector.connector.GoogleAppsDirect sailpoint.connector.OpenConnectorAdapter | | IBM i | openconnector.connector.IBMiConnector | | Lotus Domino | sailpoint.connector.LotusDomino | | JDBC | sailpoint.connector.JDBCConnector | | Sun One LDAP | sailpoint.connector.LDAPConnector | | Linux | openconnector.connector.unix.LinuxConnector sailpoint.connector.OpenConnectorAdapter sailpoint.connector.UnixConnector | | Microsoft Office365 | sailpoint.connector.Office365Connector | | Microsoft SQL Server | sailpoint.connector.mssql.serviceimpl.MSSQLServerConnectorV2 | | Okta | logger.openconnector.name = openconnector.connector.okta.OktaConnector logger.openconnector.level = debug logger.openconnector.additivity = false logger.openconnector.appenderRef.rolling.ref = STDOUT | | Oracle Database | sailpoint.connector.OracleDBConnector sailpoint.connector.JDBCConnector | | Oracle E-Business | sailpoint.connector.OracleEBSConnector sailpoint.connector.JDBCConnector | | Oracle Fusion HCM | openconnector.connector.oraclefusionhcm.OracleFusionHCMConnector sailpoint.connector.OpenConnectorAdapter | | Oracle HCM Cloud | sailpoint.connector.oraclehcmcloud.OracleHCMCloudConnector | | Oracle HRMS | sailpoint.connector.OracleAppsHRMSConnector sailpoint.connector.JDBCConnector | | Oracle Netsuite | openconnector.connector.netsuite.NetsuiteConnector | | PeopleSoft ERP | openconnector.connector.PeopleSoftConnector sailpoint.connector.OpenConnectorAdapter | | PeopleSoft HRMS | sailpoint.connector.PeopleSoftHRMSConnector | | RemedyForce | sailpoint.connector.ForceConnector | | RSA Authentication Manager | openconnector.connector.RSAConnector openconnector.connector.rsa.RSAHTTPClient sailpoint.connector.OpenConnectorAdapter | | Salesforce | sailpoint.connector.ForceConnector | | SAP Concur | openconnector.connector.sapconcur.SAPConcurConnector | | SAP - Direct | sailpoint.connector.SAPConnector sailpoint.connector.SAPInternalConnector | | SAP GRC | logger.SAPGRCConnector.name = sailpoint.connector.sapgrc logger.SAPGRCConnector.level = debug logger.SAPGRCConnector.additivity = false logger.SAPGRCConnector.appenderRef.rolling.ref = STDOUT | | SAP HR/HCM | sailpoint.connector.SAPHRInternalConnector | | SCIM 1.1 | openconnector.connector.SCIMConnector sailpoint.connector.OpenConnectorAdapter | | SCIM 2.0 | openconnector.connector.scim2.SCIM2Connector sailpoint.connector.OpenConnectorAdapter | | ServiceNow | openconnector.connector.servicenow.ServiceNowConnector openconnector.connector.servicenow.ServiceNowRestClient sailpoint.connector.OpenConnectorAdapter | | ServiceNow Service Desk Integration | openconnector.connector.servicedesk.ServiceNowServiceDeskConnector sailpoint.connector.OpenConnectorAdapter | | Siebel | openconnector.connector.SiebelConnector sailpoint.connector.OpenConnectorAdapter | | Snowflake | openconnector.connector.snowflake.SnowflakeConnector sailpoint.connector.OpenConnectorAdapter | | Solaris | openconnector.connector.unix.SolarisConnector openconnector.connector.unix.UnixConnector sailpoint.connector.OpenConnectorAdapter | | SuccessFactors | sailpoint.connector.SuccessFactorsConnector | | Sybase | sailpoint.connector.SybaseDirectConnector sailpoint.connector.JDBCConnector | | Webex | openconnector.connector.Webex sailpoint.connector.OpenConnectorAdapter | | Workday | openconnector.connector.WorkDay sailpoint.connector.OpenConnectorAdapter | | Workday Accounts | openconnector.connector.workdayaccounts openconnector.connector.workdayaccounts.WorkdayAccountsConnector sailpoint.connector.OpenConnectorAdapter | | Web Services | sailpoint.connector.WebServices | | XML | openconnector.connector.XMLConnector sailpoint.connector.OpenConnectorAdapter | | Yammer | openconnector.connector.YammerConnector sailpoint.connector.OpenConnectorAdapter | | Zoom | openconnector.connector.zoom.ZoomConnector sailpoint.connector.OpenConnectorAdapter | # 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]() ## Unable to aggregate disabled users, users who have no email ID, or users with other data-related issues You can configure user accounts in the Delinea Secret Server source so that the connector can aggregate them without an email ID. Refer to the following Delinea Secret Server documentation resources for additional information, [Data Acquisition](). ## Enabling the PUT method for provisioning operations **Resolution**: To enable the PUT method for all provisioning operations, follow these steps: 1. Configure the following parameter in the application via the REST API: Set the `usePatch` value to `false`. This is a boolean flag. 2. Send PUT request to update the connector [Update Source](). 3. For more information, refer to [Get Source Schema by ID](). # Timeout Errors and Settings Timeout errors might occur when SailPoint is waiting for a response from the Virtual Appliance (VA). These errors are applicable to all connectors and tend to occur during the setup of sources or when sources are down. This document is designed to give specific information that can be used to resolve these errors. Each timeout attribute has a default time value that is listed in seconds or minutes. Increasing the time value may resolve the error as it will allow for longer communication time between the two systems, thus avoiding the timeout error. > [!IMPORTANT] > > Add the necessary attributes or values before performing the "replace" operation, as missing attributes will cause the operation to fail. To increase the communication time, increase the value of the appropriate timeout attribute. Then submit the change to the VA using the SailPoint REST API. > [!NOTE] > > For more information on SailPoint's REST APIs, refer to [Best Practices: REST API Authentication]() and [REST API - Update Source (Partial)]() in the SailPoint Developer Community. ### aggregateTimeout **Description:** This parameter is set for the aggregation timeout, measured in seconds. **Resolution:** Increase the `aggregateTimeout` value gradually to optimize aggregation. Start with 180, then increase to 600, 900, and finally 1800. The maximum value is 3600 seconds. For example: If your current time value is 180 seconds, update the `aggregateTimeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/aggregateTimeout", "value": 600 } ] ``` ### healthCheckTimeout **Description:** This parameter is set for the test connection and health check timeout. **Resolution:** The default value is 30 seconds. If the timeout error continues, increase the value in 15 second increments and try again. For example: If your current time value is 30 seconds, update the `healthCheckTimeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/healthCheckTimeout", "value": 45 } ] ``` ### provisioningTimeout **Description:** This parameter is set for provisioning timeout. **Resolution:** Increase the `provisioningTimeout` value gradually to optimize provisioning. Start with 180, then increase to 360, and finally 600. The maximum value is 600 seconds. For example: If your current time value is 180 seconds, update the `provisioningTimeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/provisioningTimeout", "value": 360 } ] ``` ### timeout **Description:** This parameter is set for pass-through authentication timeout. **Resolution:** The default value is 15 seconds. If the timeout error continues, increase this value in 15 second increments and try again. For example: If your current time value is 15 seconds, update the `timeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/timeout", "value": 30 } ] ``` ### apiTimeout **Description:** This parameter is set for API time tracking; customers can check it using an external tool. **Resolution:** The default value is 60 seconds. If the error continues, increase the value by 15 second increments and try again. For example: If your current time value is 60 seconds, update the `apiTimeout` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/apiTimeout", "value": "75" } ] ``` ### timeoutInSeconds **Description:** This parameter helps prevent the VA from waiting indefinitely for an API response, ensuring efficient handling of API requests. For example: If your current time value is 30 seconds, update the `timeoutInSeconds` attribute as follows: ```json [ { "op": "replace", "path": "/connectorAttributes/timeoutInSeconds", "value": "15" } ] ```