# SailPoint Oracle Fusion HCM Accounts Connector Documentation > Oracle Fusion HCM Accounts Connector Documentation # Documentation # Connecting SailPoint and Oracle Fusion HCM Accounts To connect SailPoint with Oracle Fusion HCM Accounts, 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 to connect and interact with the source. > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() To configure connection settings, complete the following: 1. Go to **Connection Settings**. 2. Enter the **Base URL** in the following format: `https://.com`. This is the unique end point URL to connect to the Oracle Fusion HCM system through API. > **Note** > > SailPoint recommends using HTTPS for a secured connection. 3. For **Authentication Type**, select **Basic Authentication** or **OAuth 2.0 JWT User Assertion**. **Basic Authentication** is the default. > **Note** > > Existing basic authentication configurations continue to work without changes. - **Basic Authentication** Enter the **User Name** and **Password** of the user that connects with the Oracle Fusion HCM application. - **OAuth 2.0 JWT User Assertion** > **Screenshot** > > [![Connection settings with OAuth 2.0 JWT User Assertion selected]()]() > **Note** > > One signing certificate signs both the user assertion and the client assertion. For Oracle-side setup, refer to [Configuring OAuth 2.0 JWT User Assertion](<#configuring-oauth-20-jwt-user-assertion>). Provide the following details: - **User Name** - The user name is the subject of the user assertion. Enter the identity-domain **Username**. Use that value when the username and email differ. - **OAuth Token URL** - Enter the Oracle token endpoint that receives the user assertion and the client assertion. - **OAuth Client ID** - Enter the **Client ID** from the confidential application OAuth configuration page. Do not use the Fusion service parameter `IDCS_CONNECTOR_CLIENT_ID`. - **OAuth Scope** - Enter the Fusion Applications client scope. Copy it from the confidential application **Resources** table, or from the Fusion service parameter `IDCS_CONNECTOR_CLIENT_SCOPE`. Scope values differ by instance. Do not rebuild the string from a screenshot. Do not use the Spectra / Oracle BOSS scope `urn:opc:resource:fusion::boss/`. - **OAuth Audience** - Enter the audience expected by Oracle Identity Cloud Service. The audience is the JWT `aud` claim, normally `https://identity.oraclecloud.com/`. It is separate from the Fusion primary audience used inside the scope. - **Signing Key ID** - Enter the certificate alias (`kid`). - **Signing Private Key** - Enter the PEM-formatted private key. - (Optional) **Private Key Passphrase** - If the signing private key is encrypted, enter its passphrase. 4. (Optional) Enter the **Connection Timeout** in minutes (1 - 999). The default is 1 minute. 5. Select **Save**. ### Configuring OAuth 2.0 JWT User Assertion Follow [Configure OAuth to Access Oracle Fusion Cloud Applications REST APIs](), section **Configure OAuth Using User Assertion Grant Type**. > [!NOTE] > > Do not change the name of the OAuth token issuer. #### Identifying the Identity Domain and Token URL 1. Sign in to the OCI Identity and Access Management console as an administrator of the identity domain associated with the Fusion Applications instance. 2. Open that domain and copy the **Domain URL** from the domain details page. 3. The **OAuth Token URL** is the **Domain URL** plus `/oauth2/v1/token`. The same endpoint is listed in `https:///.well-known/idcs-configuration`. #### Registering the Confidential Application 1. In that identity domain, open **Integrated applications** and select **Add application**. 2. Select **Confidential Application** and select **Launch workflow**. 3. Enter an application name. Skip the other fields and select **Submit**. 4. In **OAuth configuration**, select **Edit OAuth**, then **Configure this application as a client now**. 5. Under **Authorization**, select only **JWT assertion**. 6. Under **Client type**, select **Trusted**. A trusted client can request access tokens with a signed JWT assertion. 7. Select **Import certificate** and import the public signing certificate that matches the private key stored in SailPoint. Set the certificate alias to the JWT Key Identifier (`kid`). That alias is the connector **Signing Key ID**. 8. Under **Token issuance policy**, set **Authorized resources** to **specific**. 9. Turn on **Add resources**. Select **Add scope**, select **Oracle Applications Cloud (Fusion)**, and add the Fusion client scope described in Generating the OAuth Scope. Remove any resource that is not required. 10. From the **Actions** menu, select **Activate**, then **Activate application**. 11. On the OAuth configuration page, copy the **Client ID**. That value is the connector **OAuth Client ID**. Do not use the Fusion service parameter `IDCS_CONNECTOR_CLIENT_ID`. Also import the same public certificate in the same domain under **Security** \> **Trusted partner certificates**, using the same alias as the JWT `kid`. Oracle stores one certificate on the confidential application. The connector uses the matching private key to sign both the user assertion and the client assertion. #### Generating the OAuth Scope The connector **OAuth Scope** is the Fusion Applications client scope. Do not use the Spectra / Oracle BOSS scope (`urn:opc:resource:fusion::boss/`). 1. In the same identity domain, open **Oracle Cloud Services** and select **Oracle Applications Cloud (Fusion)**. 2. Go to **OAuth configuration** \> **Configure application APIs that need to be OAuth protected** \> **Scopes**. 3. Copy the primary audience. Oracle shows it in one of these forms: - `urn:opc:resource:fa:instanceid=` - `urn:opc:resource:faaas:fa:` 4. Copy the resource scope. For this connector, use `urn:opc:resource:consumer::all`. 5. Concatenate the primary audience and the resource scope with no space and no extra slash. For example: `urn:opc:resource:fa:instanceid=urn:opc:resource:consumer::all` 6. Add that exact string on the confidential application **Resources** list. 7. Enter the same string in the connector **OAuth Scope** field. Copy it from the **Resources** table, or from the Fusion service parameter `IDCS_CONNECTOR_CLIENT_SCOPE`. Scope values differ by instance. Do not rebuild the string from a screenshot. **OAuth Audience** is the JWT `aud` claim, normally `https://identity.oraclecloud.com/`. It is separate from the Fusion primary audience used inside the scope. #### Mapping Oracle Values to Connector Fields | Oracle Value | Connector Field | | --- | --- | | **Domain URL** + `/oauth2/v1/token` | OAuth Token URL | | Confidential Application Client ID | OAuth Client ID | | Primary audience concatenated with `urn:opc:resource:consumer::all` | OAuth Scope | | `https://identity.oraclecloud.com/` | OAuth Audience | | Certificate alias (`kid`) | Signing Key ID | | Matching private key | Signing Private Key | | Identity-domain **Username** | User Name (user assertion subject) | The API username must be the identity-domain **Username**. Use that value when the username and email differ. ## Aggregation Settings For more information about aggregation, refer to [Loading Account Data](). Provide the settings for your aggregation. > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() To configure your aggregation, complete the following: 1. (Optional) Enter the **Page Size** to specify the number of records to display per page. The default is 50. 2. (Optional) Enter the **Users Filter** to use during aggregation. For example, to filter user names that start with "Sam", enter the following: `userName sw "Sam"` 3. (Optional) Enter the **Roles Filter** to use during aggregation. For example, to filter roles with a display name that starts with "A", enter the following: `displayName sw "A"` 4. (Optional) Enter the **Terminate Operation Messages** to stop the aggregation. The default value is Planned Outage. For example, to stop the aggregation when there is planned maintenance for Oracle, enter the following: `Planned Outage`. 5. Select **Save**. ## JSONPath Attribute Mapping The source schema for the Oracle Fusion HCM Accounts source is used to configure the objects returned from the source. The Oracle Fusion HCM Accounts supports aggregating fields in addition to those in the default account schema in the user interface. The default configuration includes JSONPath mappings for all out-of-the-box attributes. > [!NOTE] > > **Screenshot** > > [![JSONPath Attribute Mapping]()]() To fetch the additional attributes in the account aggregation, complete the following: 1. Add the attribute in the **Account Schema** and in the **JSONPath**. For example, to fetch the `preferredLanguage` attribute, add the attribute in the **Account Schema** field and add the JSONPath for the attribute in the **JSONPath** field as follows: - Schema Attribute: `preferredLanguage` - JSONPath: `preferredLanguage` 2. To add multiple attributes, select **Add Another**, and to delete an attribute select the trashcan icon. 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. # Integrating SailPoint with Oracle Fusion HCM Accounts The Oracle Fusion HCM Accounts aggregates Oracle Fusion HCM account records from an Oracle Fusion HCM cloud system and performs provisioning operations, including creating and updating accounts, changing passwords, adding or removing roles, and enabling or disabling accounts. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features The Oracle Fusion HCM Accounts connector supports the following features: ### Account Management - Manage Oracle Fusion HCM accounts as Accounts - Aggregation ### Entitlement Management - Manage Oracle Fusion HCM data role, abstract role, and job role as Entitlements - Aggregate Roles ### Provisioning - Create Account - Update Account - Enable, Disable - Change Password - Add or Remove Roles - Delete Account ### Update Account Operation The update account operation is supported for the following attributes: - `userName` - `active` - `name.familyName` - `name.givenName` - `emails` ## Prerequisites - An Oracle Fusion HCM administrator account and password for connecting to the given URL of the Oracle Fusion HCM tenant. ## Required Permissions To perform all operations, complete the following and assign the required permissions: 1. Create a single Job Role with a unique name. 2. Add the following Functional Security Policy to the Job Role you created: - Reset Password - Use REST Service - Identity Integration - Use REST Service - User Accounts - Use REST Service - users and Roles Lists of Values - Link User Account 3. Assign the Job Role to a Service Account. # Provisioning The Oracle Fusion HCM Accounts connector supports provisioning, allowing you to create and manage accounts and entitlements in Oracle Fusion HCM Accounts 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 | Account Attribute | Description | | --- | --- | | userName | The user's user name. | | active | When set to `true`, this attribute sets the user as active when creating an account. Set the value using the Static transform. By default, this is set to `false`. | | emails.work.primary.value | The user's work email. | | name.familyName | The user's family name. | | name.givenName | The user's given name. | # 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 Oracle Fusion HCM Accounts 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 | ### Default Account Attributes The Oracle Fusion HCM Accounts 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 | | --- | --- | | id | The user's ID. This is an Account ID which must not be changed. | | userName | The user's username. | | displayName | The user's display name. | | name.familyName | The user's family name. | | name.givenName | The user's given name. | | accountType | The user's account type. | | active | The user's account status. | | businessUnit | The name of the business unit the user is assigned to. | | department | The name of the department the user is assigned to. | | emails.work.primary.value | The user's work email. | | job | The user's job title. | | manager | The name of the user's manager. | | partyNumber | The user's party number. | | partyUsage | The user's party usage. | | personNumber | The person number that is linked to the user's account. | | roles | Roles associated with the user. | | userCategory | The user's category. | # Migrate VA-based Source to a SaaS Source Some sources that are connected to virtual appliance (VA) clusters can be migrated to SaaS connections. This ensures data (users and entitlements) remain intact and can maintains your source configurations like access profiles, roles, password settings, and correlation configurations when switching from a VA cluster to a SaaS connection. To migrate a source from a VA-based source to a SaaS source, you will provide configuration details on a draft version of the source before publishing the source. > [!NOTE] > > - You must have an Admin or Source Admin user level to migrate a source. A draft version of the source is created. As your migration process is in progress the live source will continue to work as it is. For more information on the Oracle Fusion HCM Accounts SaaS connector, refer to the [Oracle Fusion HCM Accounts SaaS Supported Features](). ## Important Considerations Before Migrating - You do not need to edit additional configurations (other than connection credentials) to migrate the source. - If your source migration is in progress, please do not make any configuration changes to your live source as those can be overwritten once you apply the migration your draft version. - Once you've gone ahead with your migration, it can't be rolled back. Your source is permanently migrated to a SaaS source. - Any preview operations or configuration changes on the draft source will not impact the live source until you apply the migration. ## Migrating Sources To migrate your source, complete the following: 1. Go to **Admin \> Connections \> Sources**. 2. Select or edit the VA-based source you want to migrate. 3. Open the source configuration, and select **Migrate to SaaS**. 4. When prompted, select **Continue**. A draft version of the source is created. The live source will continue to work. 5. Select **Connection Settings**. 6. Re-enter encrypted configuration details. For example, you might need to re-enter the Client Secret, Password, Refresh Token, Personal Access Token (PAT), or Certificates to migrate from the VA cluster to the SaaS connection. > **Important** > > Avoid editing the other configuration options in the draft source. 7. Select **Review and Test**. 8. Select **Test Connection**. 9. (Optional) Select **Accounts**. If you successfully tested your connection in **Review and Test**, you can select **Preview** to display a subset of accounts from the application that will be mapped to SailPoint identities. This can help ensure you are accurately connecting identity data from the application with SailPoint identities. 10. (Optional) Select **Entitlements**. If you successfully tested your connection in **Review and Test** and your source type supports entitlement type configuration, you can select **Preview** to view a preview of entitlements using the current configuration settings. 11. When you've finished reviewing your changes and successfully tested your connection, select **Apply Migration**. Your changes will be applied to the live source and the draft source will be deleted. ## Viewing Source Migration Status You can view the status and creation date of draft sources. 1. Go to **Admin \> Connections \> Sources \> Source Migration Status**. 2. Select **Source Migration Status**. 3. To view or edit the draft source, select **Actions** ![]() **\> Preview** on the draft source. 4. To delete the draft source, select **Actions** ![]() **\> Delete** on the draft source. # 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]() ## Create or Update Account Operation Fails with an Error Message The operation fails with the following error message: ```text [ InvalidRequestException ] [ Possible suggestions ] Please check if provided payload has valid attributes [ Error details ] Error while performing operation : Create Account Error code : 400 { "Errors" : [ { "description" : "Invalid, syntactically incorrect or unparseable input provided: department", "code" : "400", "uri" : "urn:oracle:apps:scim:errors:1.0:input:invalid" } ] } ``` **Resolution**: Ensure that the provided payload has valid attributes. Use the supported attributes for create and update operations. ## Create or Update Operation Fails with an Error Message When Passing the personNumber in the Provisioning Plan The operation fails with the following error message when the PersonNumber being passed in the provisioning plan has multiple work relationships. ```text Applying List binding LOV_PersonNumber with given set of values leads to multiple matching rows for a row of type:UserAccount, key oracle.jbo.Key[ 300000020907599 null null null ``` **Resolution**: Add the following attribute using [REST API - Update Source (Partial)]() and then try creating a user with the personNumber. Key = `provisionPersonId` Value = `true` `provisionPersonId` is a boolean attribute. > [!NOTE] > > Ensure that you pass the valid `personNumber` in the provisioning plan. It should not be the existing assigned `personNumber` that is assigned to other accounts. ## Create Operation Fails with an Error Message When Passing the personNumber in the Provisioning Plan The operation fails with the following error message: ```text ["openconnector.ConnectorException: Error while performing operation : Create Account Error code : 409 { "Errors" : [ { "description" : "Exception in IIP API: Ldap request processing failed - PER_IIP_220: An user with username 1213278@sndrvrtest.com already exists in Identity Store", "code" : "409" } ] }"] ``` OR ```text openconnector.InvalidRequestException: [ InvalidRequestException ] [ Possible suggestions ] Please check if provided payload has valid attributes [ Error details ] Error while performing operation : Create Account Error code : 400 { "Errors" : [ { "description" : "Invalid, syntactically incorrect or unparseable input provided: department", "code" : "400", "uri" : "urn:oracle:apps:scim:errors:1.0:input:invalid" } ] } ``` OR ```text Applying List binding LOV_PersonNumber with given set of values ``` **Resolution**: Add the following attribute using the [REST API - Update Source (Partial)](): - Key= `retryWaitTime` Value= `60000` in ms, default: 30000 ms - Key=`maxRetryCount` Value=`3`, default: 3 - Key=`retryableErrors` Value=\[`error messages`\] > [!NOTE] > > - The default error message is, "`Applying List binding LOV_PersonNumber with given set of values`". If you do not mention any other error message, the connector will use the default error message and retry. > - Ensure to pass the valid `personNumber` in the provisioning plan and it should not be the existing assigned `personNumber` (that is, assigned to other accounts). # 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" } ] ```