13 Configuring an Identity Store with Multiple Directories

This chapter explains how to prepare directories other than Oracle Internet Directory for use as an Identity Store for Fusion Application deployments.

This chapter contains the following topics:

Section 13.1, "Overview of Configuring Multiple Directories as an Identity Store"
Section 13.2, "Configuring Multiple Directories as an Identity Store: Split Profile"
Section 13.3, "Configuring Multiple Directories as an Identity Store: Distinct User and Group Populations in Multiple Directories"

13.1 Overview of Configuring Multiple Directories as an Identity Store

You must extend directory schema in the back end in order to support Oracle Access Manager-specific schema elements and other Fusion Application-specific attributes. Oracle has chosen not to extend the back end directory schema for Fusion Application deployments by default because of enterprise deployment policies that restrict the extension of schema elements in the back end directory.

In deployments where the back-end schema extension is not allowed in the enterprise Identity Store, use Oracle Internet Directory as a shadow directory and use Oracle Virtual Directory to merge the entities from the directories. The configuration requirements for such deployments is described in Section 13.2, "Configuring Multiple Directories as an Identity Store: Split Profile."

Some deployments might have users and groups divided into two different sets, for example, internal and external. Configuration requirements for such deployments is described in Section 13.3, "Configuring Multiple Directories as an Identity Store: Distinct User and Group Populations in Multiple Directories."

In this chapter, Active Directory is chosen as the non-Oracle Internet Directory Enterprise Directory. The solution is applicable to all enterprises having one or more Active Directories as their enterprise Identity Store.

13.2 Configuring Multiple Directories as an Identity Store: Split Profile

This section describes how to configure multiple directories as an Identity Store. In cases where the enterprise directory schema is not extended for Fusion Applications, Oracle Internet Directory is used as a shadow directory to store these attributes. Oracle Virtual Directory links them together to present a single consolidated DIT view to clients. This is called a split profile or split directory configuration, and it was described in Section 2.1.2, "About the Directory Tier."

You can configure Oracle Virtual Directory adapters either before or after Fusion Application provisioning. For ease of use, Oracle recommends that you perform this step after Fusion Applications provisioning.

In this configuration, all the Oracle specific attributes and Oracle specific entities are created in Oracle Internet Directory.

This section contains the following topics:

Section 13.2.1, "Prerequisites"
Section 13.2.2, "Repository Descriptions"
Section 13.2.3, "Setting Up Oracle Internet Directory as a Shadow Directory"
Section 13.2.4, "Directory Structure Overview - Shadow Join"
Section 13.2.5, "Configuring Oracle Virtual Directory Adapters for Split Profile"
Section 13.2.6, "Configuring a Global Consolidated Changelog Plug-in"
Section 13.2.7, "Validating the Oracle Virtual Directory Changelog"

13.2.1 Prerequisites

The following assumptions and rules apply to this deployment topology:

Oracle Internet Directory houses the Fusion Identity Store. This means that Oracle Internet Directory is the store for all Fusion Application specific artifacts. The artifacts include a set of enterprise roles used by Fusion Application and some user attributes required by Fusion Applications. All other stores are referred to as enterprise Identity Stores.
The enterprise contains more than one LDAP directory. Each directory contains a distinct set of users and roles.
The enterprise policy specifies that Fusion Application-specific attributes cannot be stored in the enterprise directory. All the extended attributes must be stored in a separate directory called the shadow directory. This shadow directory must be Oracle Internet Directory because Active Directory does not allow you to extend the schema.
User login IDs are unique across the directories. There is no overlap of the user login IDs between these directories.
Oracle Identity Manager has no fine-grained authorization. If Oracle Identity Manager's mapping rules allow it to use one specific subtree of a directory, then it can perform all CRUD (Create, Read, Update, Delete) operations in that subtree of the LDAP directory. There is no way to enable Oracle Identity Manager to read user data in a subtree but not enable it to create a user or delete a user in subtree.
Referential integrity must be turned off in Oracle Internet Directory so that an Oracle Internet Directory group can have members that are in one of the Active Directory directories. The users group memberships are not maintained across the directories with referential integrity.

13.2.2 Repository Descriptions

This section describesall the Oracle Fusion Applications-specific artifacts in the Identity store and how they can be distributed between Active Directory and Oracle Internet Directory, based on different enterprise deployment requirements.

The Artifacts that are stored in the Identity Store for Fusion Applications consumption are:

Application IDs: These are the identities that are required to authenticate applications to communicate with each other.
Seeded Enterprise Roles: These are the enterprise roles or LDAP group entries that are required for default functionality of Fusion Applications.
Enterprise roles provisioned by Oracle Identity Manager: These are runtime roles created by Fusion Applications.
Enterprise Users: These are the actual users in the enterprise where Fusion Applications are deployed.
Enterprise Groups: These are the roles and groups that already exist in the enterprise where Fusion Applications are deployed.

In a split profile deployment, the Identity Store artifacts related to Fusion applications can be distributed among Active Directory and Oracle Internet Directory, as follows.

Oracle Internet Directory is a repository for enterprise roles. Specifically, Oracle Internet Directory contains the following:
- Application IDs
- Seeded enterprise roles
- Enterprise roles provisioned by Oracle Identity Manager
Active Directory is the repository for:
- Enterprise users
- Enterprise groups (not visible to Oracle Identity Manager)

The following limitations apply:

The Active Directory users must be members of Oracle Internet Directory groups.
The groups in Active Directory are not exposed at all. Oracle applications only manage the Oracle-created enterprise roles. The groups in Active Directory are not visible to either Oracle Identity Manager or Fusion Applications.

13.2.3 Setting Up Oracle Internet Directory as a Shadow Directory

In cases where Oracle Internet Directory is used as the shadow directory to store all the Fusion Application-specific attributes, use a separate container in Oracle Internet Directory to store the shadow attributes.

The Shadow Entries container (cn=shadowentries) must be in a separate DIT from the parent of the users and groups container dc=mycompany,dc=com, as shown in Figure 13-1.

The same ACL configured for dc=mycompany,dc=com within Oracle Internet Directory must be configured for cn=shadowentries. To perform this configuration, use the ldapmodify command. The syntax is as follows:

ldapmodify -D cn=orcladmin -q -p portNum -h hostname -f ldifFile

The following is a sample LDIF file to use with ldapmodify:

dn: cn=shadowentries
changetype: modify
add: orclaci
orclaci: access to entry by group="cn=RealmAdministrators,cn=groups,cn=OracleContext,dc=mycompany,dc=com" (browse,add,delete)
orclaci: access to attr=(*) by group="cn=RealmAdministrators,cn=groups,cn=OracleContext,dc=mycompany,dc=com" (read, write, search, compare)
orclaci: access to entry by group="cn=OIMAdministrators,cn=groups,dc=mycompany,dc=com" (browse,add,delete)
orclaci: access to attr = (*) by group="cn=OIMAdministrators,cn=groups,dc=mycompany,dc=com" (search,read,compare,write)
-
changetype: modify
add: orclentrylevelaci
orclentrylevelaci: access to entry by * (browse,noadd,nodelete)
orclentrylevelaci: access to attr=(*) by * (read,search,nowrite,nocompare)

If you have more than one directory for which Oracle Internet Directory is used as a Shadow directory, then you must create different shadow containers for each of the directories. The container name can be chosen to uniquely identify the specific directory for which this is a shadow entry.

13.2.4 Directory Structure Overview - Shadow Join

Figure 13-1 shows the directory structure in the primary store (Active Directory and Fusion Applications Identity Store (Oracle Internet Directory).

Figure 13-1 Directory Structure

Surrounding text describes Figure 13-1 .

Figure 13-2 shows how the DIT appears to a user or client application.

Figure 13-2 Client View of the DIT

Surrounding text describes Figure 13-2 .

Figure 13-3 summarizes the adapters and plug-ins.

Figure 13-3 Adapter and Plug-in Configuration

Surrounding text describes Figure 13-3 .

13.2.5 Configuring Oracle Virtual Directory Adapters for Split Profile

In order to produce the client side view of the data shown in Figure 13-2, you must configure multiple adapters in Oracle Virtual Directory following the steps in this section.

You can use idmConfigTool to create the adapters to facilitate this configuration.

13.2.6 Configuring a Global Consolidated Changelog Plug-in

Deploy a global level consolidated changelog plug-in to handle changelog entries from all the Changelog Adapters.

In a web browser, go to Oracle Directory Services Manager (ODSM).
Connect to an Oracle Virtual Directory instance.
On the Home page, click the Advanced tab. The Advanced navigation tree appears.
Expand Global Plugins
Click the Create Plug-In button. The Plug-In dialog box appears.
Enter a name for the Plug-in in the Name field.
Select the plug-in class ConsolidatedChglogPlugin from the list.
Click OK.
Click Apply.

13.2.7 Validating the Oracle Virtual Directory Changelog

Run the following command to validate that the changelog adapter is working:

$IDM_ORACLE_HOME/bin/ldapsearch -p 6501 -D cn=orcladmin -q -b 'cn=changelog' -s base 'objectclass=*' lastchangenumber

The command should return a changelog result, such as:

Please enter bind password:
cn=Changelog
lastChangeNumber=changelog_OID:190048;changelog_AD1:363878

If ldapsearch does not return a changelog result, double check the changelog adapter configuration.

13.3 Configuring Multiple Directories as an Identity Store: Distinct User and Group Populations in Multiple Directories

In this configuration, Oracle-specific entries are stored in Oracle Internet Directory. Enterprise-specific entries are stored in Active Directory. If Fusion Applications-specific attributes are stored in Active Directory, extend the Active Directory schema as described in Section 11.5.2.2, "Configuring Active Directory for Use with Oracle Access Manager and Oracle Identity Manager."

Note:

The Oracle Internet Directory that is to be used is not necessarily the PolicyStore Oracle Internet Directory. Conceptually, a non-Active Directory directory can be used as the second directory. For convenience, this section refers to the Policy Store Oracle Internet Directory.

The following conditions are assumed:

Enterprise Directory Identity data is in one or more directories. Application-specific attributes of users and groups are stored in the Enterprise Directory.
Application-specific entries are in the Application Directory. AppIDs and Enterprise Roles are stored in the Application Directory,

This section contains the following topics:

Section 13.3.1, "Directory Structure Overview for Distinct User and Group Populations in Multiple Directories"
Section 13.3.2, "Configuring Oracle Virtual Directory Adapters for Distinct User and Group Populations in Multiple Directories"
Section 13.3.3, "Creating a Global Plug-in"

13.3.1 Directory Structure Overview for Distinct User and Group Populations in Multiple Directories

Figure 13-4 shows the directory structure in the two directories, listed here as internal and external.

Figure 13-4 Directory Structure

Surrounding text describes Figure 13-4 .

Oracle Virtual Directory makes multiple directories look like a single DIT to a user or client application, as shown in Figure 13-5.

Figure 13-5 Client View of the DIT

Surrounding text describes Figure 13-5 .

Figure 13-6 provides an overview of the adapter configuration.

Figure 13-6 Configuration Overview

Surrounding text describes Figure 13-6 .

13.3.2 Configuring Oracle Virtual Directory Adapters for Distinct User and Group Populations in Multiple Directories

Create the user adapter on the Oracle Virtual Directory instances running on OVDHOST1 and OVDHOST2 individually, as described in the following sections

13.3.2.1 Create Enterprise Directory Adapters

Create Oracle Virtual Directory adapters for the Enterprise Directory. The type of adapter that is created will be dependent on whether or not the back end directory resides in Oracle Internet Directory or Active Directory.

You can use idmconfgTool to create the Oracle Virtual Directory User and Changelog adapters for Oracle Internet Directory and Active Directory.

13.3.2.2 Create Application Directory Adapters

Create Oracle Virtual Directory adapters for the Application Directory. The back end directory for the application directory is always Oracle Internet Directory.

You can use idmconfgTool to create the Oracle Virtual Directory User and Changelog adapters for Oracle Internet Directory and Active Directory. Oracle Identity Manager requires adapters. It is highly recommended, though not mandatory, that you use Oracle Virtual Directory to connect to Oracle Internet Directory.

To do this, perform the following tasks on IDMHOST1:

Set the environment variables: MW_HOME, JAVA_HOME, IDM_HOME and ORACLE_HOME.

Set IDM_HOME to IDM_ORACLE_HOME

Set ORACLE_HOME to IAM_ORACLE_HOME
Create a properties file for the adapter you are configuring called ovd1.props. The contents of this file is as follows.

Oracle Internet Directory adapter properties file:
```
ovd.host:ovdhost1.mycompany.com
ovd.port:8899
ovd.binddn:cn=orcladmin
ovd.password:ovdpassword
ovd.oamenabled:true
ovd.ssl:true
ldap1.type:OID
ldap1.host:oididstore.us.oracle.com
ldap1.port:3060
ldap1.binddn:cn=oimLDAP,cn=systemids,dc=mycompany,dc=com
ldap1.password:oidpassword
ldap1.ssl:false
ldap1.base:dc=mycompany,dc=com
ldap1.ovd.base:dc=mycompany,dc=com
usecase.type: single
```
The following list describes the parameters used in the properties file.
- ovd.host is the host name of a server running Oracle Virtual Directory.
- ovd.port is the https port used to access Oracle Virtual Directory.
- ovd.binddn is the user DN you use to connect to Oracle Virtual Directory.
- ovd.password is the password for the DN you use to connect to Oracle Virtual Directory.
- ovd.oamenabled is always true in Fusion Applications deployments.
- ovd.ssl is set to true, as you are using an https port.
- ldap1.type is set to OID for the Oracle Internet Directory back end directory or set to AD for the Active Directory back end directory.
- ldap1.host is the host on which back end directory is located. Use the load balancer name.
- ldap1.port is the port used to communicate with the back end directory.
- ldap1.binddn is the bind DN of the oimLDAP user.
- ldap1.password is the password of the oimLDAP user
- ldap1.ssl is set to true if you are using the back end's SSL connection, and otherwise set to false. This should always be set to true when an adapter is being created for AD.
- ldap1.base is the base location in the directory tree.
- ldap1.ovd.base is the mapped location in Oracle Virtual Directory.
- usecase.type is set to Single when using a single directory type.
Configure the adapter by using the idmConfigTool command, which is located at:

IAM_ORACLE_HOME/idmtools/bin

Note:

When you run the idmConfigTool, it creates or appends to the file idmDomainConfig.param. This file is generated in the same directory that the idmConfigTool is run from. To ensure that each time the tool is run, the same file is appended to, always run the idmConfigTool from the directory:

IAM_ORACLE_HOME/idmtools/bin

The syntax of the command on Linux is:
```
idmConfigTool.sh -configOVD input_file=configfile [log_file=logfile]
```
The syntax on Windows is:
```
idmConfigTool.bat -configOVD input_file=configfile [log_file=logfile]
```
For example:
```
idmConfigTool.sh -configOVD input_file=ovd1.props
```
The command requires no input. The output looks like this:
```
The tool has completed its operation. Details have been logged to logfile
```

Run this command on each Oracle Virtual Directory host in your topology, with the appropriate value for ovd.host in the property file.

13.3.3 Creating a Global Plug-in

To create a Global Oracle Virtual Directory plug-in, proceed as follows:

In a web browser, go to Oracle Directory Services Manager (ODSM) at the URL listed in Section 21.2, "About Identity Management Console URLs."
Create connections to each of the Oracle Virtual Directory instances running on OVDHOST1 and OVDHOST2, if they do not already exist.
Connect to each Oracle Virtual Directory instance by using the appropriate connection entry.
On the Home page, click the Advanced tab. The Advanced navigation tree appears.
Click the + next to Global Plugins in the left pane.
Click Create Plugin.
Create the Global Consolidated Changelog Plug-in as follows:

Enter the following values to create the Global Consolidated Plug-in:
- Name: Global Consolidated Changelog
- Class: Click Select then choose: ConsolidatedChangelog
Click OK when finished.

The environment is now ready to be configured to work with Oracle Virtual Directory as the Identity Store.