Configure Integration Between Oracle Access Governance and SAP SuccessFactors

Prerequisites

Before you install and configure a SAP SuccessFactors Orchestrated System, you should consider the following prerequisites and tasks.

  1. Your SAP SuccessFactors system is certified with Oracle Access Governance. Refer to Components Certified for Integration with Oracle Access Governance for details of the versions supported.

Configure

You can establish a connection between SAP SuccessFactors and Oracle Access Governance by entering connection details. To achieve this, use the orchestrated systems functionality available in the Oracle Access Governance Console.

Navigate to the Orchestrated Systems Page

The Orchestrated Systems page of the Oracle Access Governance Console is where you start configuration of your orchestrated system.

Navigate to the Orchestrated Systems page of the Oracle Access Governance Console, by following these steps:
  1. From the Oracle Access Governance navigation menu icon Navigation menu, select Service Administration → Orchestrated Systems.
  2. Click the Add an orchestrated system button to start the workflow.

Select system

On the Select system step of the workflow, you can specify which type of system you would like to integrate with Oracle Access Governance.

You can search for the required system by name using the Search field.

  1. Select SAP SuccessFactors.
  2. Click Next.

Add details

Add details such as name, description, and configuration mode.

On the Add Details step of the workflow, enter the details for the orchestrated system:
  1. Enter a name for the system you want to connect to in the Name field.
  2. Enter a description for the system in the Description field.
  3. Determine if this orchestrated system is an authoritative source, and if Oracle Access Governance can manage permissions by setting the following checkboxes.
    • This is the authoritative source for my identities
    • I want to manage permissions for this system
    The default value in each case is Unselected.
  4. Click Next.

Add Owners

Add primary and additional owners to your orchestrated system to allow them to manage resources.

You can associate resource ownership by adding primary and additional owners. This drives self-service as these owners can then manage (read, update or delete) the resources that they own. By default, the resource creator is designated as the resource owner. You can assign one primary owner and up to 20 additional owners for the resources.

Note:

When setting up the first Orchestrated System for your service instance, you can assign owners only after you enable the identities from the Manage Identities section.
To add owners:
  1. Select an Oracle Access Governance active user as the primary owner in the Who is the primary owner? field.
  2. Select one or more additional owners in the Who else owns it? list. You can add up to 20 additional owners for the resource.
You can view the Primary Owner in the list. All the owners can view and manage the resources that they own.

Account settings

Outline details of how to manage account settings when setting up your orchestrated system including notification settings, and default actions when an identity moves or leaves your organization.

On the Account settings step of the workflow, enter details of how you would like to manage accounts with Oracle Access Governance when configured as a managed system:
  1. Select whether to allow Oracle Access Governance to create accounts when a permission is requested, if the account does not already exist. By default this option is selected meaning that an account will be created if it does not exist, when a request for a permission is made. If the option is unselected then permissions can only be provisioned where the account already exists in the orchestrated system. If permission is requested where no user exists then the operation will fail.
  2. Select where to send notification emails when an account is created. The default setting is User. You can select one, both, or none of these options. If you select no options then notifications will not be sent when an account is created.
    • User
    • User manager
  3. When an identity leaves your enterprise you should remove access to their accounts. You can select what to do with the account when this happens. Select one of the following options:
    • Delete
    • Disable
    • No action
  4. When all permissions for an account are removed, for example when moving from one department to another, you may need to adjust what accounts the identity has access to. You can select what to do with the account when this happens. Select one of the following options:
    • Delete
    • Disable
    • No action
  5. If you want Oracle Access Governance to manage accounts created directly in the orchestrated system you can select the Include accounts that are not created by Access Governance option. This will reconcile accounts created in the target system and will allow you to manage them from Oracle Access Governance.

Note:

If you do not configure your system as a managed system then this step in the workflow will display but is not enabled. In this case you proceed directly to the Integration settings step of the workflow.

Note:

If your orchestrated system requires dynamic schema discovery, as with the Generic REST and Database Application Tables integrations, then only the notification email destination can be set (User, Usermanager) when creating the orchestrated system. You cannot set the disable/delete rules for movers and leavers. To do this you need to create the orchestrated system, and then update the account settings as described in Configure Orchestrated System Account Settings.

Integration settings

Enter details of the connection to your SAP SuccessFactors system.

  1. On the Integration settings step of the workflow, enter the details required to allow Oracle Access Governance to connect to your SAP SuccessFactors system.

    Table - Integration settings

    Parameter Name Mandatory? Description

    Account Type

    Yes
    Select what type of account you want to integrate from your SAP SuccessFactors system. This can be one of the following options:
    • User
    • Employee
    This option applies when your SAP SuccessFactors orchestrated system is running in authoritative source mode. The identity attributes supported will vary dependent on account type. See Supported Attributes for details of available identity attributes in each case.
    What is the base URL for SuccessFactors? Yes The URL to access your SAP SuccessFactors system. For example:
    <http|https://<hostname>/successfactors.com:<port>
    What is the company ID? Yes Company ID is a short string of characters that identifies each SAP SuccessFactors system. It is used during login to validate your access token and for provisioning operations.

    What is the authentication server url to validate the client?

    		 Yes
    URL of the authentication server that validates credentials for the target system. For example:
    https://<hostname>/successfactors.com/oauth/token
    ).

    What is the authorization server url?

    		 Yes Required only when a private key is used to generate a SAML token, for example:
    https://<hostname>/successfactors.com/oauth/idp

    What is the client ID?

    		 Yes ID issued by the authorization server when registering your client.

    What is the authentication mechanism?

    		 Yes Select from one of the following:
    • SAML Assertion Token
    • Private Key

    What is the SAML assertion?

    		 No If authentication mechanism selected is SAML Assertion Token then enter the SAML token issued by the trusted IDP for your client.

    What is the private key?

    		 No If authentication mechanism selected is Private Key then enter the encrypted private key .

    What is the username?

    		 No Required only when a private key is used to generate a SAML token
  2. Click Add to create the orchestrated system.

Finish Up

Finish up configuration of your orchestrated system by providing details of whether to perform further customization, or activate and run a data load.

The final step of the workflow is Finish Up.

You are given a choice whether to further configure your orchestrated system before running a data load, or accept the default configuration and initiate a data load. Select one from:
  • Customize before enabling the system for data loads
  • Activate and prepare the data load with the provided defaults

Post Configuration

There are no post configuration steps associated with the SAP SuccessFactors system.