# SailPoint Oracle Fusion HCM Accounts SaaS Connector Documentation > Oracle Fusion HCM Accounts SaaS Connector Documentation # Documentation # Connecting SailPoint and Oracle Fusion HCM Accounts SaaS 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 **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. (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](). 4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** section. 5. 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. (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](). 5. 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](). 6. 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. (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](). 4. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 5. (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](). 6. (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. 7. 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]()]() [![Aggregation Settings]()]() [![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 SaaS 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**. ## Activity Insights Settings SailPoint pulls in activity data in the form of events like user logins, password changes, and content updates within the application. You can view an identity’s activity data within an application to discover trends for that user. > [!IMPORTANT] > > Contact your SailPoint Customer Success Manager (CSM) for more information on Activity Insights. For more information on utilizing activity data, refer to [Activity Insights](). Activity Insights Settings allows you to gather account information and activity data from Oracle Fusion HCM Accounts. To enable Activity Insights for the Oracle Fusion HCM Accounts application, refer to [Prerequisites]() for more information. To configure Activity Insights, complete the following: > [!NOTE] > > **Screenshot** > > [![Activity Insights Settings]()]() 1. Go to **Activity Insights Settings**. 2. Select **Enable Activity Insights** to view access to data insights on source and application activity such as logins and other app-specific events. 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 SaaS The Oracle Fusion HCM Accounts SaaS 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 SaaS 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` ### Activity Insights Activity Insights supports activity from Oracle Fusion HCM Accounts and its associated accounts. This allows you to gather account information and activity data from Oracle Fusion HCM Accounts. > [!IMPORTANT] > > Contact your SailPoint Customer Success Manager (CSM) for more information on Activity Insights. For more information on configuring Activity Insights, refer to Activity Insights Settings. For more information on SailPoint features, refer to [Source Features](). ## 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 SaaS 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 SaaS connector uses the following default correlation and object configurations. ## Default Correlation Configuration Before you aggregate accounts from this source, you can map account attributes with their corresponding identity attributes based on your requirements. You can customize the correlation configuration. Refer to [Assigning Source Accounts to Identities]() for more information. When you first create the Oracle Fusion HCM Accounts SaaS source, the default correlation mapping is: | Account Attribute | Operation | Identity Attribute | | --- | --- | --- | | username | Equals | Name | ## 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 SaaS 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. | # 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]() ## Debug Logs For information about managing additional source settings, including debug logging and downloading connector logs, refer to [Managing Additional Settings](). ## 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.