# SailPoint Atlassian Data Center Connector Documentation > Atlassian Data Center Connector Documentation # Documentation # Connecting SailPoint and Atlassian Data Center To connect SailPoint with Atlassian Data Center, 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 Provide the information required for SailPoint to connect and interact with Atlassian Data Center. > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() Choose the appropriate **Authentication Type** and provide the information required to connect and interact with the source. The following Authentication Types are supported: - Basic Authentication - Personal Access Token Authentication ### Basic Authentication > [!NOTE] > > **Screenshot** > > [![Basic Authentication connection settings]()]() 1. Provide the **Host URL** for the source. For example: `https://contoso.example.com:8443/Atlassian` 2. Enter the **Username** and **Password** to authenticate with the source. 3. Select **Save**. ### Personal Access Authentication > [!NOTE] > > **Screenshot** > > [![Personal Access Token connection settings]()]() 1. Provide the **Host URL** for the source. For example: `https://contoso.example.com:8443/Atlassian` 2. Enter the **Personal Access Token** to authenticate with the source. 3. Select **Auto Refresh Personal Access Token** to enable the connector to create a new personal access token automatically before the current token expires. - Enter your **Token Name**. Token Name must be unique and contain no more than 30 characters. - In the **Days until Expiry** field, enter the number of days after which the token will expire. The default is 90 days. The minimum value is 1 and the maximum value is 365. 4. Select **Save**. ## Additional Settings On the **Additional Settings** page, configure the advance settings as well as aggregation settings. > [!NOTE] > > SailPoint recommends that you do not change the default settings. Changing the settings could result in performance issues. ### Aggregation Settings In the **Additional Settings \> Aggregation Settings** section, configure the aggregation settings such as filter and page size. Use a semicolon delimiter to add multiple filter conditions. For more information about aggregation, refer to [Loading Account Data](). > [!NOTE] > > **Screenshot** > > [![Additional Settings aggregation]()]() [![Additional Settings]()]() 1. (Optional) Select **Include Inactive Accounts** to aggregate inactive users as well. 2. (Optional) Enter **Account Filter** to filter the accounts during aggregation. Only strings are supported as a filter condition. For multiple conditions, use a semicolon delimiter. For example, use the following to retrieve only those accounts with a display name that starts with `john` or `chris`. `john;chris` 3. (Optional) In the **Page Size** field, enter the number of records per page. The default is 50 records per page. The minimum value is 1 and the maximum is 1000. 4. Enable **Aggregate Accounts from File** to aggregate accounts from Atlassian Data Center Version 10.X and later. 5. Enable **Use Data Center Host Configuration for SFTP** to apply the Data Center host settings( SFTP Host, Username and Password) for establishing a secure SFTP configuration. 6. In **SFTP Host**, enter the Host Name/IP address of the server. 7. In **SFTP Port**, enter the port number to connect to server. 8. Enter the **Username** to log into the SFTP server during file transfer. 9. Enter the **Password** to authenticate to the SFTP server during file transfer. 10. In **Location of Account Details File** field, enter the absolute path. `/C:/Data/Accounts/.csv` ### Advanced Settings In the **Additional Settings \> Advanced Settings** section, you can provide settings for Thread Count and Connection Timeout. > [!NOTE] > > **Screenshot** > > [![Advanced Settings]()]() 1. (Optional) In the **Thread Count** field, enter the maximum number of threads for account aggregation. The default is 8. 2. (Optional) Enter the **Connection Timeout** in minutes to hold the HTTP connection with the Atlassian system in an idle state. The default is 1. 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. # Enable Direct Permissions Direct permission is a right an admin gets that provides detailed access to other accounts. It allows rights to create, read, or update an object such as a file or an application. Enabling direct permission with an entitlement improves governance insights, such as: - Allows admins to see what actions a user can perform with the access granted by an entitlement. - Allows admins to create more effective access profiles and roles. - Allows reviewers to make necessary decisions on certifications. # Integrating SailPoint with Atlassian Data Center Atlassian is a leading product company providing tools for collaboration and service desk. The SailPoint Atlassian Data Center connector supports reading and provisioning of Atlassian users and groups. Use the Atlassian Data Center source in SailPoint to manage Atlassian Data Center user accounts. After you successfully configure the connector, your organization will be able to aggregate and provision accounts for Jira users and manage access to other Atlassian products such as, Confluence, Jira Service Management, Bitbucket, and Bamboo by managing memberships of groups having access to respective products. This guide is designed to give specific information about the requirements and field definitions needed to get a working instance of the Atlassian Data Center connector. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features > [!NOTE] > > Before you can use any feature marked with an asterisk (\*), SailPoint must activate the feature for your site. The Atlassian Data Center connector supports the following features: - Aggregation of accounts - \*Provision the accounts - Create - Enable and Disable ( Managed accounts only) - Delete - Add and Remove Entitlements - \*Access Certifications (certification of entitlements connected to accounts) - \*Password Management For more information on features, refer to [Source Features](). The Atlassian Data Center connector supports multiple group objects and direct permissions. The following table provides details on each feature: | Feature | Users | | --- | --- | | Aggregate | ✔ | | Create | ✔ | | Password Management | ✔ | | Group Entitlements (Read, Request, Revoke) | Groups, Project Roles | | [Enable Direct Permissions]() | ✔ | ### Group Entitlements Group Entitlements are the entitlement types which aggregate additional details of entitlement types from the managed system. These objects have separate schema defining list of attributes that aggregation task fetches as additional details when aggregation is run for that Group Entitlements type. | Feature | Groups | Project Roles | | --- | --- | --- | | Aggregation | ✔ | ✔ | ### Password Management If Password Management is enabled for your organization, you can change the password for a user of the source. After enabling password management on the source, be aware of the following: - The password policy defined in SailPoint applies to accounts on this source. - If you change the password for an application connected to this source, the change will automatically be made to the source itself. For more information on configuring password management, refer to [Password Management Overview](). ## Prerequisites - Configure at least one virtual appliance cluster and successfully test the connection. For more information, refer to the [Virtual Appliance Reference Guide](). - A Service account that is a member of the Jira administrators group is required for basic authentication and Personal Access Token authentication. - All Atlassian products that you want to be managed using this connector must be connected to a single Jira server for centralized user management. - For Atlassian Data Center version 10.x, a server with SFTP access must be set up to allow connections for transferring files required for account aggregation. ### Basic Authentication The service account is authorized using Basic Authentication, which requires a username and password. It is generated by a user account with Administrator access. A service account that is a member of the Jira administrators group is required for Basic Authentication. ### Personal Access Token Authentication The service account is authorized using Personal Access Token (PAT) authentication. The token is encoded and generated by a user account with Administrator access. It is then added to the headers for API requests. To enable the **Auto Refresh Personal Access Token**, the authentication type must be set to Personal Access Token. #### Creating a Personal Access Token 1. In Jira, select your profile picture at the top right corner of the screen. 2. Select **Profile**. 3. Select **Personal Access Tokens** from the left-hand menu. 4. Select **Create Token**. 5. Give your new token a name. ### SFTP Based Account Aggregation From Atlassian Data Center version 10.x onwards, the API-based user aggregation method is no longer supported. To enable account aggregation, an **SFTP based setup** is required. This requires uploading a CSV file containing user details, extracted from the Atlassian database to the SFTP server. > [!IMPORTANT] > > When exporting CSV files, use UTF-8 without BOM encoding. #### Steps for File Based Account Aggregation (Data Center 10.X Onwards Only) 1. Set Up a SFTP host. 2. Create an Access-Controlled Folder. 3. Extract User Details from Atlassian Data Center's Database. > **Note** > > The Extracted file must have user\_name, display\_name, email\_address, active. The column names must match these exactly to work correctly. 4. Use the following MySQL query to extract the required user details: ```sql SELECT 'user_name' , 'display_name', 'email_address', 'active' UNION ALL SELECT u.user_name, u.display_name, u.email_address, CASE WHEN u.active = 1 THEN 1 WHEN u.active = 0 THEN 0 WHEN u.active = 'Active' THEN 1 WHEN u.active = 'Inactive' THEN 0 END AS active FROM cwd_user u JOIN cwd_directory d ON u.directory_id = d.id INTO OUTFILE '/.csv' FIELDS TERMINATED BY ',' ENCLOSED BY '"' LINES TERMINATED BY '\n'; ``` 5. Configure the file path and SFTP Connection Credentials in Aggregation Settings. > [!NOTE] > > For sources created prior to March 2025, when changing the authentication type to Personal Access Token (PAT), update the following entry in your source XML using the V3 Source API: > > `` ## Required Permissions To manage certain features in the source, set permissions in the following list. - The service account must be a Super Admin User (Site Admin/Jira-administrators) with an API Token created on the target managed system. - The service account must have the required permissions to access the host via **SFTP** to retrieve the CSV file containing user details. If the use of a service account is not preferred, an alternative user account with the necessary permissions can be created. ## Supported Managed Systems The Atlassian Data Center connector supports the following Atlassian products: - Atlassian Jira Service Management: 10.3.1 - Jira Software: 10.3.4 - Confluence: 9.2.0 - Bamboo: 10.2.3 - Bitbucket: 9.4.5 # Provisioning The Atlassian Data Center connector supports provisioning, allowing you to create and manage accounts and entitlements in Atlassian Data Center directly from SailPoint. **Prerequisite:** Your system is configured for provisioning. When SailPoint provisions new accounts to the source, it uses the attributes on the **Create Account** page as instructions or a template for what to include in the account. This page is also referred to as the *provisioning policy*. When new access is granted on a source where a user does not already have an account, SailPoint automatically includes account creation in the provisioning. This applies whether provisioning is started from an access request or from an automated role or lifecycle state assignment. For direct-connect sources, SailPoint automatically creates the account from this configuration. If the source is not configured as a direct-connect source, SailPoint creates and assigns a provisioning task to the source owner and includes the values for the source owner to use in manually creating the account. > [!IMPORTANT] > > This section describes the default **Create Account** configuration. SailPoint recommends that you work with Services to define a provisioning configuration specific to your company's needs. Be sure to verify large changes to the provisioning policy before implementation. Failure to do so might cause provisioning to fail. ## Default Create Account Attributes The following generators create the required information for a new Atlassian Suite account: | Create Account Attributes | Identity Attribute | Description | | --- | --- | --- | | name | Create Unique Account ID | The user name of an Atlassian Jira software user | | emailAddress | Work Email | The email address of the user | | displayName | Display Name | The display name of the user | | password | Disable | The password of the user | | notification | Disable | This sends an email to the user that you want to create. The notification will enable the user to set password. By default, it is set to false and a notification is not sent. | > [!NOTE] > > If there is any issue with the aggregation of the `emailAddress` attribute, note that the `emailAddress` attribute is aggregated only for accounts from those domains that belong to the service account's domain. # 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 Atlassian Data Center connector uses the following default correlation and object configurations. > [!NOTE] > > The Atlassian Data Center connector only supports the schema attributes covered in the following topics: ## 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 | | --- | --- | | name | Account | | name | Group | | projectRoleId | Project Role | ### Default Account Attributes The Atlassian Data Center 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 | | --- | --- | | name | A unique identifier for a Jira user. Username of Atlassian Jira Software user. This is an Account ID which must not be changed. | | displayName | The display name of the user. | | emailAddress | The email address of the user. | | timeZone | The time zone of the user. | | locale | The default location of the user for purpose of localizing items. | | groups | The list of groups that the user belongs to. | | projectRoles | The list of roles that the user belongs to. | ## 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 Atlassian Data Center connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups. | Attribute Name | Description | | --- | --- | | name | The name of the group. This is an Account ID which must not be changed. | | labels | The description (labels) of the group. | ### Default Project Role Attributes | Attribute Name | Description | | --- | --- | | name | The name of the Project Role. | | displayName | The display name of the Project Role. | | projectRoleID | A unique identifier for the project specific roles. This is an Account ID which must not be changed. | | id | A unique identifier for the Project Role. | | description | The description of the Project Role. | # 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]() # 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" } ] ```