6 Oracle Directory Integration Platform

This chapter describes issues associated with Oracle Directory Integration Platform. It includes the following topics:

6.1 General Issues and Workarounds

This section describes general issues and workarounds. It includes the following topics:

6.1.1 Enabling the Domain-Wide Administration Port on Oracle WebLogic Server Prevents use of the DIP Command Line Interface

Be aware that enabling the domain-wide administration port on any WebLogic server running Directory Integration Platform will prevent you from using the DIP command line interface using a standard administrator account. Entering DIP commands will result in an error similar to the following:

User: "weblogic", failed to be authenticated

Administrators can still use the Enterprise Manager (EM) GUI to configure and manage Oracle Directory Integration Platform.

6.1.2 LDIF Files That Contain Non-ASCII Characters Will Cause the testProfile Command Option to Fail if the LDIF File has Native Encoding

When running DIP Tester from a command-line, the manageSyncProfiles testProfile command will fail if the -ldiffile option is specified and the LDIF file contains non-ASCII characters.

Note that LDIF files with UTF-8 encoding are not impacted by this limitation. If an LDIF file containing multibyte characters cannot be saved with UTF-8 encoding, then use the following workaround:

  1. From a command-line, add the entry using the ldapadd command and include the -E option to specify the locale. See the Oracle Fusion Middleware User Reference for Oracle Identity Management for the required command syntax.

  2. Get the specific changeNumber for the last add operation.

  3. Execute the testProfile command using the changeNumber from the previous step.

    For more information, see the section "10.1.5.2 Running DIP Tester From the WLST Command-Line Interface" in the Oracle Fusion Middleware Administrator's Guide for Oracle Directory Integration Platform.

6.1.3 Running the testProfile Command with LDIF Files Option Fails in Advance Mode

When running DIP Tester from a command-line in advance mode, the manageSyncProfiles testProfile command will fail if the -ldiffile option is specified and may synchronize the wrong operation. To resolve this issue, run the manageSyncProfile updatechgnum command.

For more information, see the section "10.1.5.2 Running DIP Tester From the WLST Command-Line Interface" in the Oracle Fusion Middleware Administrator's Guide for Oracle Directory Integration Platform.

6.1.4 Some Changes May Not Get Synchronized Due to Race Condition in Heavily-Loaded Source Directory

If the source directory is heavily-loaded, a race condition may occur where database commits cannot keep pace with updates to the lastchangenumber. If this race condition occurs, Oracle Directory Integration Platform may not be able to synchronize some of the changes.

Note:

This issue only occurs if you are using Oracle Internet Directory as the back-end directory.

To work around this issue, perform the following steps to enable database commits to keep pace with the lastchangenumber:

  1. Increase the value of the synchronization profile's Scheduling Interval.

  2. Control the number of times the search is performed on the source directory during a synchronization cycle by setting the searchDeltaSize parameter in the profile. Oracle suggests starting with a value of 10, then adjusting the value as needed.

6.1.5 manageSyncProfiles Utility Prompts for Wrong Password

When you run the manageSyncProfiles utility to synchronize with a database, the manageSyncProfiles register prompts for the connected directory password. Ensure that you specify the connected database password and not the directory password.

6.1.6 Schema Error Messages may Appear after Upgrade

After upgrading from Oracle Directory Integration Platform 11.1.1.7.0 environment, when you run the dipConfigurator update command successfully, it may throw schema error messages. You can ignore these messages.

Note:

This issue only occurs if you are using Oracle Unified Directory or Oracle Directory Server Enterprise Edition as the back-end directory.

6.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

6.2.1 If Oracle Internet Directory is the Back-End Directory then do not use localhost as Oracle Internet Directory Hostname When Configuring Oracle Directory Integration Platform

When configuring Oracle Directory Integration Platform against an existing Oracle Internet Directory—using either the installer's Install and Configure installation option or the Oracle Identity Management 11g Release 1 (11.1.1) Configuration Wizard—you must specify the hostname for Oracle Internet Directory using only its fully qualified domain name (such as myhost.example.com). Do not use localhost as the Oracle Internet Directory hostname even if Oracle Directory Integration Platform and Oracle Internet Directory are collocated on the same host.

If you use localhost as the Oracle Internet Directory hostname, you will not be able to start the Oracle WebLogic Managed Server hosting Oracle Directory Integration Platform.

6.2.2 You may Need to Restart the Directory Integration Platform After Running dipConfigurator Against Oracle Unified Directory

After running dipConfigurator against an Oracle Unified Directory (OUD) endpoint, if you are unable to open the Directory Integration Platform (DIP) UI in Enterprise Manger, stop and start DIP to fix the UI problem.

6.2.3 When Configuring a Profile, you may Need to Scroll Past a Section of Whitespace to View Mapping Rules

If you are using Internet Explorer to view the Directory Integration Platform (DIP) UI, you may need to scroll past a large blank space to see the profile mapping rules section. This issue is not known to affect other browsers.

6.2.4 Resource Usage Charts will not Display if Multiple IDM Domains are Running on the Same Host

If two IDM domains on the same host share the same Oracle home and are both configured to use wls_ods1 managed servers, then the DIP home page will not display the resource usage charts if both instances are running at the same time.

6.3 Provisioning Issues

This section describes provisioning issues. It includes the following topics:

6.3.1 Modification may not Propagate Using Interface Protocol (Inbound) Version 3.0

When an inbound provisioning profile with interface protocol version 3.0 is configured with Oracle Internet Directory (Back-End Directory), then modification fails to propagate. For more information, see http://support.oracle.com/.

6.3.2 Provisioning from Oracle Internet Directory (Back-End Directory) to an Application May Fail

If you delete a provisioning profile for Oracle Internet Directory, and recreate it with same name, then the provisioning from Oracle Internet Directory to an application may fail. To resolve this issue, create a provisioning profile and specify a new name. For more information on creating a provisioning profile, see "Managing Provisioning Profiles Using manageProvProfiles" in the Oracle Fusion Middleware Administrator's Guide for Oracle Directory Integration Platform.

6.4 Documentation Errata

There are no known documentation issues at this time.