Configure Integration with SAP User Management (UM)

Prerequisites

Before you install and configure a SAP User Management (UM) Orchestrated System, you should consider the following prerequisites and tasks.

Certification

  1. Check that your SAP User Management (UM) system is certified with Oracle Access Governance by referring to Components Certified for Integration with Oracle Access Governance for details of the versions supported.

Create a Service User Account

Oracle Access Governance requires a user account to access the SAP User Management (UM) system during service operations. Depending on the system you are using, you can create the user in your managed system and assign specific groups, roles, parameters, and profiles to the user.

Create a Service User Account for Orchestrated System Operations in SAP User Management (UM)

To create the SAP User Management (UM) user account for operations:

  1. Create a CPIC User with the S_IDOC_ALL profile.
  2. Add the following authorizations along with the corresponding default parameter values:
    • S_RFC
    • S_TABU_DIS
    • S_TABU_NAM
    • S_USER_AGR
    • S_USER_AUT
    • S_USER_GRP
    • S_USER_PRO
    • S_USER_SAS
    • S_USER_SYS
  3. Modify the parameter values as follows:

    For S_RFC

    • ACTVT: 16
    • RFC_NAME: *
    • RFC_TYPE: FUGR

    For S_TABU_DIS

    • ACTVT: 03,02
    • DICBERCLS: SUSR,*

    For S_TABU_NAM

    • ACTVT: 03,02
    • TABLE: USH*,USR*,USZ*,AGR_TEXTS

    For For S_USER_AGR

    • ACTVT: 03,22,02
    • ACT_GROUP: *

    For S_USER_AUT

    • ACTVT: 03
    • AUTH: *
    • OBJECT: *

    For S_USER_GRP

    • ACTVT: 01,02,03,05,06,08,22,78,PP
    • CLASS: *

    For S_USER_PRO

    • ACTVT: 03,22
    • PROFILE: *

    For S_USER_SAS

    • ACTVT: 01,06,22
    • ACT_GROUP: *
    • CLASS: *
    • PROFILE: *
    • SUBSYSTEM: *

    For S_USER_SYS

    • ACTVT: 78
    • SUBSYSTEM: *

Configure

You can establish a connection between SAP User Management (UM) 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 User Management (UM).
  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.

Note:

The SAP User Management (UM) orchestrated system allows you to manage groups in SAP User Management (UM) using the I want to manage identity collections for this orchestrated system option. If selected, this checkbox allows you to manage SAP User Management (UM) groups from within Oracle Access Governance. Any changes made to SAP User Management (UM) groups will be reconciled between Oracle Access Governance and the orchestrated system. Similarly, any changes made in SAP User Management (UM), will be reflected in Oracle Access Governance

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 to allow Oracle Access Governance to create new 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 permission is requested. 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 provisioning operation will fail.
  2. Select where and who 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

    Note:

    The options above are only displayed if supported in the orchestrated system type being configured. For example, if Delete is not supported, then you will only see the Disable and No action options.
  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

    Note:

    The options above are only displayed if supported in the orchestrated system type being configured. For example, if Delete is not supported, then you will only see the Disable and No action options.
  5. If you want Oracle Access Governance to manage accounts created directly in the orchestrated system you can select the Manage accounts that are not created by Access Governance option. This will reconcile accounts created in the managed 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 User Management (UM) system.

  1. On the Integration settings step of the workflow, enter the details required to allow Oracle Access Governance to connect to your SAP User Management (UM) system.

    Table - Integration settings

    Parameter Name Mandatory? Description
    What is the SAP host? Yes The hostname or IP address for the directory you want to integrate with Oracle Access Governance, for example example.com, 172.20.55.120.
    What is the SAP client? Yes The value of the SAP User Management (UM) client setting. For example, 800.
    What is SAP master system? Yes Enter the RFC Destination value that is used for identification of the SAP User Management (UM) system. This value must be same as that of the Logical System name.

    Sample value: OH2CLNT800

    The master system value is a combination of <SYSTEM_ID>CLNT<CLIENT_NUM>.

    In the preceding sample value, OH2 is the System ID of the managed system and 800 is the client number.

    What is the SAP instance number? Yes It is a two-digit identifier assigned to a SAP User Management (UM) instance during installation.

    For example 00.

    What is the destination used to interact with the SAP system? Yes Enter a unique value to establish a connection with the SAP User Management (UM) system.

    For example: dest123.

    What is the username to log into the SAP? Yes Enter the user name of the SAP User Management (UM) system.
    What is the password of the user used to log into the SAP? Yes Enter the password of the SAP User Management (UM) System.
    Confirm password Yes Confirm the password.
    What is the dummy password value? Yes Enter the dummy password that you want the managed system to use during a Create User provisioning operation. The managed system first sets the password as this value and then changes it to the password specified on the process form.
    Confirm password Yes Confirm the password.
    What is the SAP router string? No Use this parameter for a system protected by a firewall.
    Which type of roles to be reconciled? Yes Select the type of role to reconcile from SAP User Management (UM) system.
    • Both: Fetches both Single roles and Composite roles from the target.
    • Single roles: Fetches only Single roles from the target system.
    • Composite roles: Fetches only Composite roles from the target.
    Custom jar details Yes Provide the details of the sapjco3.jar file in the form of <JAR NAME>::<JAR CHECKSUM>
  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.

On the Finish Up step of the workflow, you are asked to download the agent you will use to interface between Oracle Access Governance and SAP User Management (UM). Select the Download link to download the agent zip file to the environment in which the agent will run.

After downloading the agent, follow the instructions explained in the Agent Administration article.

Pre-Startup Configuration for Agent Initialization

Before starting the agent, ensure that you have added the custom JAR to the agent and completed the following configurations in the config.json and config.properties files:

To add custom JAR:

  1. Navigate to the custom JAR folder.

    <AGENT_HOME>/<PERSISTENT_VOLUME_LOCATION>/data/customJars

  2. Add the SAPJco JAR file.

For config.json:

  1. Navigate to the default location of the config.json file.

    <AGENT_HOME>/<PERSISTENT_VOLUME_LOCATION>/data/conf/config.json

  2. Update the following property:

    "numberOfOperationsWorkerThread": 1,

For config.properties:

  1. Navigate to the default location of the config.properties file.

    <AGENT_HOME>/<PERSISTENT_VOLUME_LOCATION>/data/conf/config.properties

  2. Update the following property:

    idoConfig.numberOfOperationsWorkerThread=1

After updating the configuration files, you can start the agent.

Finally, 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 a SAP User Management (UM) system.