# SailPoint Oracle ERP Cloud Connector Documentation > Oracle ERP Cloud Connector Documentation # Documentation # Connecting SailPoint and Oracle ERP Cloud To connect SailPoint with Oracle ERP Cloud, 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 **Actions**. 5. In the **Actions** dropdown list, select the setup method: - [**Express Setup**](<#configuring-a-source-using-express-setup>) - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started. > **Note** > > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](). For more information, contact your SailPoint Customer Service Manager. - [**Standard Setup**](<#configuring-a-source-using-standard-setup>) - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup. ### Configuring a Source Using Express Setup Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data. 1. Review the directions and select **Start Express Setup**. 2. Review the pre-populated **Source Name**, **Source Owner**, and **Description**. To update, select **Edit**. > **Note** > > The source name must be unique. You can change these settings later in the source configuration. 3. Select **Virtual Appliance**. A virtual appliance is a Linux-based virtual machine that connects to your sources and apps using SailPoint APIs, connectors, and integrations. For more information about configuring and deploying virtual appliances, 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 in SailPoint, 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. For more information, refer to the **Connection Settings** section. 6. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation. - If you want to aggregate now, select **Aggregate**. - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**. - To see the list of aggregated source accounts, go to **Account Management \> Accounts**. - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet. ### Configuring a Source Using Standard Setup Use Standard Setup to configure the connector for full feature support. 1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters. 2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters. 3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](). 4. 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. 5. 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. 6. (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](). 7. 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](). 8. 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 The following information is required for SailPoint to connect and interact with Oracle ERP Cloud. > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() 1. Select **Connection Settings** from the menu. 2. Enter the unique end point URL in **Host URL**. 3. Enter the **Username** and **Password** of the service account. 4. Select **Save**. ## Aggregation Settings Set the aggregation settings for the Oracle ERP Cloud connector. For more information about aggregation, refer to [Loading Account Data](). > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() 1. Select **Aggregation Settings** from the menu. 2. Enter the **Page Size** as the number of records to fetch per page. The default is 100 records per page. 3. Enter the **User Filter**. The User Filter is a query used to filter accounts during account aggregation. For example, you can use the username `sw "A"` query to retrieve only those accounts whose names start with A. By default, the filter is `Active eq true`, which aggregates only the active users. 4. Enter the **Role Filter**. The Role Filter is a query used to filter roles during entitlement aggregation. For example, you can use the `Category eq "JOB" query`. This filter aggregates roles of only the Job category. By default, the Oracle ERP Cloud source aggregates roles of the following types: - Job - Data - Abstract 5. Select **Save**. ## Additional Settings Set additional settings for the Oracle ERP Cloud server: - Connection timeout - Data access delimiter config attribute - Retry count - Retry after duration > [!NOTE] > > **Screenshot** > > [![Additional Settings]()]() 1. Select **Additional Settings** from the menu. 2. Enter the **Connection Timeout** in minutes. This is the allowed duration within which the connection to the Oracle ERP Cloud system must be established. The default is 1 minute. 3. Set the **Data Access Delimiter** character. By default, the character is `$`. In the following example, the Data Access entitlement is aggregated as: `Accounts Payable Manager:Business unit:Account_BU` - Use `connector_data_access_delimiter` key with the value as "`:`" In the following example, the Data Access entitlement is aggregated as: `Value Accounts Payable Manager|Business unit|Account_BU` - Use the `connector_data_access_delimiter` key with the value as "`|`" 4. Enable **Use previous REST framework version's for Data Securities** if you may experience issues with security data access due to special characters. It is enabled by default. 5. Enter the **Retry Count**. This configures the number of times your system tries to connect to the Oracle ERP Cloud server if it encounters a Service Unavailable error (`Error Code: 503`). By default, your system retries three (3) times. 6. Enter the duration of time (in minutes) that your system should wait between retry attempts if it encounters a Service Unavailable error (`Error Code: 503`) into the **Retry After (Minute)** field. By default, the system waits for one (1) minute between retry attempts. 7. 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. # Data Access Aggregation Settings The **Data Access Aggregation** feature supports aggregation of all security context and security context values (data access) from the Oracle ERP Cloud managed system. This feature should only be used if required. Enabling the feature may seriously impact system performance. If the feature is not required, skip this step. If the feature is required, refer to the following information: > [!WARNING] > > Enabling the **Data Access Aggregation** feature may seriously impact the system performance. It is advised to use this feature only if required. ## Use Previous REST Framework Version's for Data Securities Enable **enableOldRestFrameworkForDataSecurities** for handling special characters in the Data Access. By default, the value is set as false. entry to the source XML using the REST APIs: - Key: `enableOldRestFrameworkForDataSecurities` - Value: `true` > [!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. ## Supported Security Contexts | Context Name | Module | | --- | --- | | [AssetBook]() | Financials | | [Business Unit]() | Financials, Procurement | | [Data access set]() | Financials | | [Intercompany Organization]() | Financials | | [Ledger]() | Financials | | [Control Budget]() | Financials | | [Project Organization Classification]() | Project Management | | [Reference Data set]() | Financials | | [Legal Entity]() | Financials | ## Minimum Permissions Required The following Function Security Policies, Role Hierarchy, and existing aggregation permissions are required to use this feature. ### Function Security Policy - to Access Security Context LOVs REST APIs | User Friendly Name of Role | Role Code | | --- | --- | | Manage Application Reference Data Set | `FND_APP_MANAGE_REFERENCE_DATA_SET_PRIV` | | Manage Application Reference Data Set Assignment | `FND_APP_MANAGE_REFERENCE_DATA_SET_ASSIGNMENT_PRIV` | | Get Enterprise Structures Using REST Service | `FUN_GET_ENTERPRISE_STRUCTURES_REST_SERVICE_PRIV` | | Get General Ledger Setups Using REST Service | `GL_GET_GENERAL_LEDGER_SETUPS_USING_REST_SERVICE_PRIV` | | Get Intercompany Setups Using REST Service | `FUN_GET_INTERCOMPANY_SETUPS_USING_REST_SERVICE_PRIV` | | Manage Control Budgets | `XCC_MANAGE_CONTROL_BUDGETS_PRIV` | | View Fixed Asset Transaction Accounting | `FA_VIEW_FIXED_ASSET_TRANSACTION_ACCOUNTING_PRIV`, `FA_VIEW_FIXED_ASSET_BOOKS_PRIV` | | Manage Project Labor Schedules | `PJC_MANAGE_PROJECT_LABOR_SCHEDULES_PRIV` | | View Purchase Order Work Area | `PO_VIEW_PURCHASING_WORKAREA_PRIV` | ### Data Security Policy - to Create a Data Security Policy | Data Resource | Value | Usage | | --- | --- | --- | | `Data Access Set for Table GL_ACCESS_SETS` | All values | Manage Access Sets (Data) | | `Control Budget` | All values | | | `Fixed Asset Book` | All values | | | `Project Organization for Table PJF_ALL_ORGANIZATIONS` | All values | | | `Business Unit` | All values | | ### Role Hierarchy - to Schedule and Access Oracle Business Intelligence Reports | Role Name | Role Code | Security for Analysis and Reports | Usage | | --- | --- | --- | --- | | BI Consumer Role | BIConsumer | View-Only | View Report | | BI Author Role | BIAuthor | Create and Edit | Reschedule Report | | BI System Role | BISystem | Access SOAP and Related services | Backend SOAP calls | | BI Application Administrator Duty Role | BIA\_ADMINISTRATOR\_DUTY | Manage Permissions | Manage report permissions and Download Report | ## Prerequisites By default, the user with BI Administrator privileges must unarchive the following archive (i.e. SailpointDAv1.catalog) located in 'Shared Folders' under Catalog of Reports and Analytics platform. Once unarchived, the new folder with 'SailpointDAv1' name should start appearing in the Shared Folders path. > [!CAUTION] > > Once unarchived, any further modification of the content in 'SailpointDAv1' folder is strictly prohibited. Download the SailpointDAv1.zip from the [SailPoint Community](). > [!IMPORTANT] > > If the path of the BI report is set to anything other than 'SailpointDAv1', it is mandatory to overwrite all the reports in the unarchived folder by recreating them with the correct data model path. Additionally, make sure in report settings that the Output Format and Default Format are set to Data (CSV) and saved. ## Enable the Data Access Aggregation Feature > [!WARNING] > > Enabling the **Data Access Aggregation** feature may seriously impact the system performance. It is advised to use this feature only if required. 1. Ensure the [Minimum Permissions Required](<#minimum-permissions-required>) have been met. 2. Ensure the [Prerequisites](<#prerequisites>) have been met. > **Screenshot** > > [![Data Access Aggregation]()]() 3. Enable the **Aggregate Data Access for Seeded Roles** and **Aggregate Data Access for Custom Roles** features based on your aggregation needs. 4. In the **Oracle Business Intelligence Report Directory Path** field, enter **SailpointDAv1**. 5. Select **Save**. > [!NOTE] > > Once the aggregation with the features enabled is complete, SailPoint advises that you disable the features to avoid system performance impacts for each consecutive aggregation attempt when data access aggregation is not required. ## Unarchive the Catalog File in the Oracle Business Intelligence Platform ### Option 1: Unarchive to Shared Folder (Default) 1. Download the SailpointDAv1.zip from the [SailPoint Community](), and unzip the download to get the SailpointDAv1.catalog file. 2. Sign in to Oracle ERP Cloud with valid BI admin's credentials. 3. Go to **Tools \> Reports and Analytics**. Ensure your browser allows pop-ups for the Reports and Analytics page, and then select the **Browse Catalog** button. The catalog window will open in a separate tab. 4. On the Catalog tab, select **Folders \> Shared Folders \> Tasks**, and then select **Unarchive**. Keep the settings as is (Replace = None, ACL = Inherit) and select **OK**. The **SailpointDAv1** folder should now be visible under **Shared Folders**. The **OracleERPCloud** folder delivers the **SailpointDAv1.catalog** file containing the data model and report files. The catalog file is an archived version of the folder from Oracle Business Intelligence with necessary permissions. > **Note** > > Once unarchived, the SailpointDAv1 folder contains two data models, **SeededRolesMapping** and **NonSeededRolesMapping** and two reports, **SeededRolesReport** and **NonSeededRolesReports**. These files are required to schedule reports needed to generate the CSV extract of Roles and Security context relationships for aggregation of data access in the connector. ### Option 2: Unarchive to Desired Folder (Custom) 1. Download the SailpointDAv1.zip from the [SailPoint Community](), and unzip the download to get the SailpointDAv1.catalog file. 2. Sign in to Oracle ERP Cloud with valid BI admin's credentials. 3. Go to **Tools \> Reports and Analytics**. Ensure your browser allows pop-ups for the Reports and Analytics page, and then select the **Browse Catalog** button. The catalog window will open in a separate tab. 4. On the Catalog tab, select **Folders**, and then select the desired folder where you want to unarchive the file. Select **Tasks**, and then select **Unarchive**. Keep the settings as is (Replace = None, ACL = Inherit) and select **OK**. 5. Confirm that a folder named SailpointDAv1 appears under the selected folder. (Optional) delete **SeededRolesReport** and **NonSeededRolesReport** files to recreate them from scratch. 6. Create Reports 1. Open **SeededRolesMapping**, and select **Edit** to access the data model. 2. Select **Create Report** to begin generating a new report. 3. In the Create Report window, locate the **SeededRolesMapping.xdm** file within the unarchived folder. Choose **Select Layout**, and select **Portrait** and **Table Layout**. 7. Design the Table Drag and drop the fields in the following order: - ROLE\_NAME - SECURITY\_CONTEXT 8. Save and View the Report 1. Save the report as **SeededRolesReport**, and select **OK** to save (or replace) and view it. 9. Set the Report Properties 1. Select **Edit Report** from the gear icon. 2. Ensure the output and default format is **Data (CSV)**. 10. Set Permissions 1. Go to the folder where you unarchived the catalog, and confirm the presence of the **SeededRolesReport**. 2. Select **More**, and then **Permissions**. Add your service user account with **Full Control** permissions to ensure proper access to schedule and read the report. 11. Repeat for Non-Seeded Roles. Follow steps 6-10 for the **NonSeededRolesMapping** data model to create the **NonSeededRolesReport**. > **Note** > > The reports must be named **SeededRolesReport** and **NonSeededRolesReport**. These reports are essential for SailPoint connector operations, ensuring proper aggregation of roles and security context data. To find the BI report directory path select **More**, and then **Schedule**. Copy the report directory path from the report name. For example, if the report name is `/~ServiceUser/DesiredFolder/SailpointDAv1/report.xdo`, the correct BIDirectoryPath will be `/~ServiceUser/DesiredFolder/SailpointDAv1` # Integrating SailPoint with Oracle ERP Cloud > [!NOTE] > > **Integration** > > This is an integration and requires additional licensing or subscriptions to utilize it. For more information, contact your customer success manager. The Oracle ERP Cloud integration with SailPoint helps in the governance of accounts and groups. End-to-end account management capabilities provide deep governance and visibility into the organization's health. - The Oracle ERP Cloud Integration Module is used to manage users, roles, and data access of Oracle ERP Cloud. - The Oracle ERP Cloud connector uses the Oracle REST APIs. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features The Oracle ERP Cloud connector supports the following features: > [!NOTE] > > Before you can use any of the following items marked with an asterisk (\*), SailPoint must activate the feature for your site. - Aggregation - Aggregate users - Aggregate abstract, data, and job roles as entitlement. The role is a group object. - Aggregate Data Access associated to users - \*Provision the accounts - Create, Update, Delete > **Note** > > To enable the delete functionality, set the `enableDeleteUserAccount` connector attribute to `true`. Refer to Delete account fails with an error message for more information. - Enable, Disable - Add / Remove Entitlement - \*Access Certifications (certification of entitlements connected to accounts) - \*Password Management For more information on features, refer to [Source Features](). ### 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](). ## Privilege Classification SailPoint Privilege Classification helps organizations systematically categorize and manage the privilege levels of entitlements within their sources. By classifying entitlements as high, medium, or low, administrators can better understand the potential risk and impact associated with specific access rights. This allows automatic assignment of privilege levels based on system recommendations, custom-defined criteria, or a same level across all entitlements. | Privilege Level | Description | | --- | --- | | High | Administrative level access to accounts | | Medium | Administrative level access for a specific role or function | | Low | Only basic access of data | > [!NOTE] > > To manage Privilege Classification, users must have administrative roles such as Org Admin, Source Admin or Source Sub-Admin. For more information, refer to [Managing Privilege Classification](). > [!NOTE] > > **Example** > > [![Recommended Privilege Level - High]()]() > > [![Recommended Privilege Level - Medium]()]() ## Prerequisites - Configure at least one [virtual appliance (VA) cluster]() and successfully test the connection. - Set up a service account that has a service role to perform all the operations. - Create a data role for create or update user with Worker Association. This data role needs to be assigned to a service account. - Required Configuration for Data Access Aggregation in the Oracle ERP Cloud: [Data Access Aggregation Settings](). ### Create a Service Role in the Oracle ERP Cloud System The Oracle ERP Cloud system requires a service account with a specially configured service role to connect with SailPoint. 1. From the Security Console, select **Create Role** to create a custom job role. 2. In the **Function Security Policies** tab, assign the following policies: - Use REST Service - Identity Integration - Use REST Service - Users and Roles Lists of Values - Manage Data Access for Users > **Note** > > This permission is required to manage Data Access. 3. View **Summary**. 4. Select **Save** and **Close**. 5. Assign the newly created role to the service account. ### Create a Data Role in Oracle ERP Cloud You must create and configure the Data Role for Worker Association. 1. Go to **Setup and Maintenance \> Search \> Manage Data Role and Security Profiles**. 2. Select **Create new Data Role** and provide a unique name for the Data Role. 3. In the **Job Role** field select **Integration Specialist**. 4. On the **Create Data Role: Security Criteria** page, select all the required data along with **Person Security Profile** set to **View All People**. 5. Review the Data Role and select **Submit**. 6. Assign the new Data Role to a **Service Account**. ## Supported Managed Systems The Oracle ERP Cloud connector supports the following version and modules: **Version** - Oracle ERP Cloud application system version 20D onward. **Modules** - Financial Management - Project Management - Procurement - Risk Management # Machine Account Attributes Machine account attributes are used in provisioning configurations for machine accounts. After you have [created the required machine account subtypes](), you can use the machine account attributes to provision machine accounts in your SailPoint tenant. Refer to [Machine Identity Security Overview]() for more information. # Provisioning The Oracle ERP Cloud connector supports provisioning, allowing you to create and manage accounts and entitlements in Oracle ERP Cloud 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 list outlines which account attributes SailPoint uses to create a profile for new Oracle ERP Cloud accounts: | Attribute Name | Description | | --- | --- | | User Name | A unique identifier for the user to authenticate with the service provider directly. This is a mandatory attribute. | | Password | The Oracle ERP Cloud password. This is a mandatory attribute. | | User Category | The user category of the user. Default: `DEFAULT`
**Note:** If you create or update an account, or if you provide an incorrect value for the user category, then the value of `User Category` is set to `DEFAULT`. | | First Name | The first name of the user. | | Last Name | The last name of the user. | | Email | The primary email address of the user. | | Person Number | The worker association information of the User.
**Note:** Providing a Person Number in the create/update operation will associate the respective worker information with a user account. You must manually add the `Person Number` attribute to existing sources. For more information, refer to [Adding Attributes to a Source Schema](). | # 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 ERP Cloud 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 ERP Cloud 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 | A unique identifier for the user resource in Oracle Applications Cloud. This is an Account ID which must not be changed. | | Display Name | The display name of the user, usually the full name. | | Email | The primary email address of the user. | | User Name | A unique identifier for the user to authenticate with the service provider directly. | | Status | Indicates the administrative status of the user. | | First Name | The first name of the user. | | Last Name | The last name of the user. | | Last Modified Date | The last modified date of the user. | | Created Date | The created date of the user. | | User Category | The user category of the user. Default: `DEFAULT` | | Account Type | The account type of a user to indicate the person or party association. | | Manager | The manager associated to the user. | | Person Number | The worker ID or person number associated to the user. | | Business Unit | The business unit to which the user belongs. | | Department | The department to which the user belongs. | | Job | The job title of the user. | | Roles | The list of roles assigned to the user. | | Data Access | Combination of role, security context, and its values assigned to the user. | ### Additional Account Attributes The Oracle ERP Cloud connector supports aggregation of additional account attributes which are part of SCIM API. The attribute name must be the same as the API response JSON path. > [!NOTE] > > The `__c` suffix must be added for additional schema attributes. Ensure that you append `__c` at the end of the attribute name. For example, if you want to add the `preferredLanguage` attribute, you must add `preferredLanguage__c`. For more information, refer to [Adding Attributes to a Source Schema](). The following attributes are supported: - `preferredLanguage__c` - `schemas__c` - `meta__c` - `urn:scim:schemas:extension:fa:2.0:faUser__c` ## 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 Oracle ERP Cloud 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 | | --- | --- | | ID | A unique identifier for the role resource in Oracle Applications Cloud. This is an Account ID which must not be changed. | | Description | The description of the role. | | Category | The category of role. | | Name | A unique identifier for the role to authenticate with the service provider directly. | | Last Modified Date | The last modified date of the role. | | Created Date | The created date of the role. | | Display Name | The display name of the role. | # 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 ERP Cloud SaaS connector, refer to the [Oracle ERP Cloud 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]() ## User or Role Filter Error The following error message displays: ```text Exception during aggregation of Object Type account on Application OracleERP. Reason: Unable to create iterator sailpoint.connector.ConnectorException: { "Errors" : [ { "description" : "PER_IIP_209:Page Mode not supported when querying against database and OID attributes", "code" : "501" } ] } ``` **Resolution**: Update the filter query to use the Oracle-supported filter combinations with pagination support. For more information on pagination and filters, refer to the [Oracle SaaS]() documentation. In the search box, type **Financials REST API manage collection**, this will provide documentation related to filters and pagination in the manage collection link. ## Delete account fails with an error message The following error message displays: ```text java.lang.UnsupportedOperationException: Delete operation is not supported. For details or troubleshooting, refer to the connector documentation. ``` **Resolution**: Set the `enableDeleteUserAccount` connector attribute to `true` on the source with the [Update Source (Partial)]() API: ```json [ { "op": "add", "path": "/connectorAttributes/enableDeleteUserAccount", "value": true } ] ``` ## Error message appears for Test Connection, Aggregation or Provisioning operations The following error message displays: ```text Exception: sailpoint.connector.ConnectorException: [ ConnectorException ] [ Error details ] javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated ``` **Resolution**: Update the openJDK version to 11.0.3 or later. ## An error message appears when assigning data access to user The following error message displays: ```text openconnector.InvalidRequestException: Role is not assigned to a user, cannot process data access: $$ ``` **Resolution**: To assign the Data Access, ensure that the corresponding role is assigned to a user. For example, to assign the **Accounts Payable ManagerBusiness unitAccount\_BU** user Data Access, you need to assign the **Accounts Payable Manager** role to it. ## Create/Modify operation fails with an error message when passing the personNumber in the provisioning plan The operation fails with the following error message: ```text Another user has changed the row with primary key oracle.jbo.Key[300000027193775 ]. ``` OR ```text Applying List binding LOV_PersonNumber with given set of values ``` **Resolution**: Add the following attribute using [REST API - Update Source (Partial)]() in SailPoint and then, try creating a user with `personNumber`. - Key= `retryWaitTime` Value= `60000` in ms, default: 30000 ms - Key=`maxRetryCount` Value=`3`, default: 3 - Key=`retryableErrors` Value=\[`error messages`\] > [!NOTE] > > The default error messages are, `Applying List binding LOV_PersonNumber with given set of values` and `Another user has changed the row with primary key`. If you do not specify any other error message, the connector will use the default error messages and retry. ## Entitlement aggregation fails with error The following error message displays: ```text Reason: java.lang.RuntimeException: An error occurred while aggregating[ InvalidConfigurationException ][ Error details ] err_msg_oracle_erp_invalid_creds ``` **Resolution**: Please review if the password of the service user contains any special characters. If yes, reset the password without any special characters and retry entitlement aggregation. ## Create/Update operation fails with LOV\_PersonNumber error **Issue**: The create/update 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)](), then try creating a user with the personNumber. Key = `provisionPersonId` Value = `true` `provisionPersonId` is an boolean attribute. > [!NOTE] > > Ensure you pass the valid `personNumber` in the provisioning plan. You should not pass the existing assigned `personNumber` assigned to other accounts. ## Provisioning fails with record combination of values error Account aggregation ad group aggregation fetch different data access. Account aggregation fetches the **description** of the security context, and group aggregation fetches the **value** of the security context. For example, group aggregation data access is fetched as `Citadel Asset Accountant$Asset book$IN CORP BOOK`. However, during account aggregation, the same access is fetched as `Citadel Asset Accountant$Asset book$CIT Corporate Asset Book IN`, which results in a provisioning error. **Issue**: Provisioning fails with error `openconnector.ConnectorException: [ ConnectorException ] [ Error details ] A record with this combination of values already exists`. **Resolution**: Make the SecurityContext **value** and SecurityContext **description** the same. For example, change the description of the Asset Book `IN CORP BOOK` from `CIT Corporate Asset Book IN` to `IN CORP BOOK`. Once the value and description are the same, try aggregation/provisioning again. # 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" } ] ```