Integrate with Oracle Unified Directory

The Oracle Unified Directory connector integrates Oracle Access Governance with Oracle Unified Directory. You can establish a connection between Oracle Unified Directory and Oracle Access Governance by entering connection details and configuring the connector. To achieve this, use the Orchestrated Systems functionality available in the Oracle Access Governance Console.

Preinstall

Before you install and configure an Oracle Unified Directory orchestrated system, you should consider the following pre-requisites and tasks.

Certified Components

The system can be any one of the following:

  • Oracle Unified Directory 11g 11.1.1.5.0, 11.1.2.0.0, 11.1.2.2.0, and 11.1.2.3.0
  • Oracle Unified Directory 12c 12.2.1.3.0 and 12.2.1.4.0
  • Oracle Unified Directory 14c 14.1.2.1.0

Supported Operations (Authoritative)

The Oracle Unified Directory orchestrated system supports the following operations where Oracle Unified Directory is the authoritative source for identities:

  • Create user
  • Update user
  • Delete user
  • Enable user
  • Disable user
  • Reset password
  • Create group or organization unit
  • Update group name or organization unit name
  • Delete group or organization unit
  • Update container DN
  • Add groups
  • Revoke groups

Supported Operations (Non-Authoritative)

The Oracle Unified Directory orchestrated system supports the following operations where Oracle Unified Directory is a managed system:

  • Create user
  • Reset password
  • Add groups
  • Revoke groups

Create a System User Account for Oracle Unified Directory Orchestrated System Operations

Oracle Access Governance requires a user account to access the system during service operations. Depending on the system you are using, you can create the user in your system and assign specific permissions and roles to the user.

For Oracle Unified Directory:

You must create a system user account for performing the following functions.
  • Create, modify, and delete entries related to the managed objects, including accounts, groups, roles (if supported), and organizational units (ou).
  • Update passwords for users.
Create an admin user account on the Oracle Unified Directory system. For details of how to do this, see the relevant sections in the following:

Install

You can establish a connection between Oracle Unified Directory and Oracle Access Governance by entering connection details and configuring your OUD environment. 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, specify which type of system you would like to onboard.

  1. Select Oracle Unified Directory and click Next.

Enter details

On the Enter 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 What do you want to call this system? field.
  2. Enter a description for the system in the How do you want to describe this system? 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 Selected.
  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 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
  2. When an identity moves within your enterprise, for example when moving from one department to another, you may need to adjust what accounts the identity has access to. In some cases the identity will no longer require certain accounts which are not relevant to their new role in the enterprise. You can select what to do with the account when this happens. Select one of the following options:
    • Disable
    • Delete
  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:
    • Disable
    • Delete

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 (Oracle) 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 the target Oracle Unified Directory.

  1. In the Host field, enter the hostname or IP address for the directory you want to integrate with Oracle Access Governance.
  2. In the Port field, enter the value of the TCP/IP port number used to communicate with the LDAP server.
  3. Enter the distinguished name which you will use to authenticate to the directory, in the Administrator Username field. This is the user you created in Create a Target System User Account for Oracle Unified Directory Orchestrated System Operations.
  4. Enter the password of the target distinguished name in the Password field. Confirm the password in the Confirm password field.
  5. Enter a base context from which to begin searches for users and groups into the Base Contexts field.
  6. In the Failover field, enter a list of failover servers in the format <servername>:<port>, <servername>:<port>, ..., for example OUDExample1:636, OUDExample1:636, ...
  7. In the SSL Enabled field, ensure that the value true is selected.
  8. Check the right hand pane to view What I've selected. If you are happy with the details entered, select 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

Postinstall

There are no postinstall steps associated with a Oracle Unified Directory system.