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.

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 - 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 - 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 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.

To configure connection settings, complete the following:

1. Go to Connection Settings.

2. Enter the Base URL in the following format: https://<your Oracle cloud domain>.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

     

     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.

     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.

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://<domain-url>/.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=<fusion-instance-id>
   • urn:opc:resource:faaas:fa:<pod-system-name>

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=<fusion-instance-id>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

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.

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.

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.

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:

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.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.