Configure Integration Between Oracle Access Governance and Microsoft Active Directory

Prerequisites

Before you install and configure a Microsoft Active Directory or Microsoft Active Directory Lightweight Directory Services (AD LDS) orchestrated system, you should consider the following prerequisites and tasks.

Certification

  1. Check that your Microsoft Active Directory or Microsoft Active Directory Lightweight Directory Services (AD LDS) 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 User Account

Oracle Access Governance requires a user account to access the Microsoft Active Directory or Microsoft Active Directory Lightweight Directory Services (AD LDS) systems during service operations. Depending on the system you are using, you can create the user in your managed system and assign specific permissions and roles to the user.

Create a User Account for Orchestrated System Operations in Microsoft Active Directory

For Microsoft Active Directory:

You can use a Microsoft Windows 2008 Server (Domain Controller) administrator account for operations. Alternatively, you can create a user account and assign the minimum required rights to the user account.

To create the Microsoft Active Directory user account for operations:

See Also: Microsoft Active Directory documentation for detailed information about performing this procedure.

  1. Create a group (for example, AGGroup) on the system. While creating the group, select Security Group as the group type and Global or Universal as the group scope.

    Note:

    In a parent-child domain setup, create the group in the parent domain.
  2. Make this group a member of the Account Operators group.
  3. Assign all read permissions to this group. If there are multiple child domains in the forest, then log in to each child domain and add the above group to the Account Operators group of each child domain.

    Note:

    You assign read permissions on the Security tab of the Properties dialog box for the user account. This tab is displayed only in Advanced Features view. To switch to this view, select Advanced Features from the View menu on the Microsoft Active Directory console.
  4. Create a user (for example, AGUser) on the target system. In a parent-child domain setup, create the user in the parent domain.
  5. Make the user a member of the group (for example, AGGroup) created in Step 1.

Create a User Account for Orchestrated System Operations in Microsoft Active Directory Lightweight Directory Services (AD LDS)

For Microsoft Active Directory Lightweight Directory Services (AD LDS):

You must create and use a user account that is a member of the Administrators group for performing operations.

To create the Microsoft Active Directory Lightweight Directory Services (AD LDS) user account for operations:

See Also: Microsoft Active Directory Lightweight Directory Services (AD LDS) documentation for detailed information about performing this procedure.

  1. Create a user account in Microsoft Active Directory Lightweight Directory Services (AD LDS).
  2. Set a password for the user account.
  3. Enable the user account by setting the msDS-UserAccountDisabled field to false.
  4. Ensure that the msDS-UserDontExpirePassword and ms-DS-UserPasswordNotRequired fields are available.
  5. Enter a value in the userPrincipalName field.

    Note:

    The value must be in the format username@domain_name, for example: OAGuser@example.com.
  6. Add the user's distinguished name (DN) to the Administrators group.

Note:

To create a user account for performing operations in a standalone Microsoft Active Directory Lightweight Directory Services (AD LDS) instance, follow these steps:
  1. Create a user account in the standalone computer.
  2. Add the newly created user to the AD LDS Administrators group: CN=Administrators,CN=Roles,DC=X.

Configure

You can establish a connection between Microsoft Active Directory 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 Microsoft Active Directory.
  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 Microsoft Active Directory orchestrated system allows you to manage groups in Microsoft Active Directory using the I want to manage identity collections for this orchestrated system option. If selected, this checkbox allows you to manage Microsoft Active Directory groups from within Oracle Access Governance. Any changes made to Microsoft Active Directory groups will be reconciled between Oracle Access Governance and the orchestrated system. Similarly, any changes made in Microsoft Active Directory, 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 (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

Enter details of the connection to your Microsoft Active Directory system.

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

    Table - Integration settings

    Parameter Name Mandatory? Description
    What is the host name? 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 port number? Yes The value of the TCP/IP port number used to communicate with the LDAP server. The default is 636.
    What is the principal? Yes The distinguished name with which to authenticate the LDAP server.

    This is the user you created in Create a User Account.

    What is the password? Yes The password of the target distinguished name.
    Confirm password Yes Confirm the password.
    What is the base context? Yes Enter a base context from which to begin searches for users and groups. For example, OU=new,DC=test,DC=com.
    What is the failover server? No Enter a list of failover servers in the format <servername>:<port>, <servername>:<port>, ..., for example ADExample1:636, ADExample1:636, ....
    SSL enabled Yes Ensure that the value true is selected.

    Following are the steps to configure SSL on agent:

    1. Use JDK to install and run an agent.
    2. As part of agent installation process, copy cacerts of JDK used for agent under agent Installation directory.
    3. Import AD cert to above cacerts file using the command
      <%JAVA_HOME%>/bin/keytool -import -alias OIGAD-cert -file <AD-cert-file> -keystore <agent-install-dir>/cacerts
    4. Config.properties should include the following:
      JAVA_OPTS=-Djavax.net.ssl.trustStore=/app/cacerts-Djavax.net.ssl.trustStorePassword=changeit
    What is the domain name? Yes Name of the windows domain, for example windowsdomain.mycompany.com.
    What are the account object classes? Yes The object class or classes that will be used for creating user objects in the LDAP tree.
    What are the organization object classes? Yes Specify the object classes for organization, organizational unit, and container in Microsoft Active Directory.
    Is this Active Directory is a Lightweight Directory Services(AD LDS) environment? No Select this check box if you are configuring this as an Active Directory Lightweight Directory Services (AD LDS) instance.

    By default, it is false.

    Note: There are prerequisites for schema attributes in AD LDS. You must review Default Supported Attributes.

  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 Microsoft Active Directory. 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.

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 Microsoft Active Directory system.