Configure Integration Between Oracle Access Governance and PeopleSoft

Related Topics

Prerequisites

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

  1. Your instance is certified with Oracle Access Governance. Refer to Peoplesoft Components Certified for Integration with Oracle Access Governance for details of the versions supported.
  2. Your environment meets the requirements for certain elements to be present in your environment. See PeopleSoft Components Required For Integration for details of the requirements.

Configure

You can establish a connection between 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

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 onboard. You can search for the required system by name using the Search field.

  1. Select .
  2. Click Next.

Enter Details

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

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

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

On the Integration settings step of the workflow, enter the configuration details required to allow Oracle Access Governance to connect to .

  1. Enter the Easy Connect URL for database for connection to the PeopleSoft Oracle database.
  2. In the Database schema user name enter the name of the schema user you will use to connect to the PeopleSoft Oracle database. For details on how to create this user, refer to Configure Oracle Database Schema User Account.
  3. Enter the Database schema password for the schema user you will use to connect to the PeopleSoft Oracle database. Confirm your password in the Confirm password field.
  4. In the Url field, enter the URL of the server hosting the application server you want to integrate with. Use the format host:port, where port is the Jolt port.
  5. In the Username field, enter the username required to connect to the instance to perform data reconciliation and provisioning. For details on how to create this user, refer to Configure PeopleSoft Service Account Using Peoplesoft PIA Web Interface.
  6. In the Password and Confirm password fields enter the password that authenticates the user you are connecting to the instance with.
  7. Optionally, if you have domains configured in your instance, enter the domain password into the Domain password and Confirm password fields.
  8. In the Custom jar details field enter the details of custom jars used during integration. The files are psjoa.jar and psmanagement.jar, and should be entered in the following format:
    <jarName>::<jarChecksum>, <jarName>::<jarChecksum>

    For example:

    psjoa.jar::12345, psmanagement.jar::54321

    For more information on custom jar support, refer to Custom Jar Support.

  9. Click Add to create the orchestrated system.

Finish Up

The final step of the workflow is Finish Up where you are prompted to download the agent for your Orchestrated System. Once you have downloaded the agent, you can install and configure the agent in your environment using the instructions in Install Oracle Access Governance Agent.

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

When you have complete installation of your agent, you need to copy two Java jar files from the installation, into the agent custom JARs directory.
  1. Copy the following JAR files from your home directory (PS_HOME).
    • psjoa.jar
    • psmanagement.jar
  2. Copy the files to the agent custom JARs directory path as specified in the config.json, where /app is the agent volume. For example, you may have a value such as "customJarsDirectory": "/app/data/customJars" in your config.json.

    Note:

    If the custom JARs are not available for any reason, then the Validate operation will fail with the error message Invalid session.