| Oracle® Identity Manager Connector Guide for Novell eDirectory Release 9.0.4 Part Number E10432-05 |
|
|
View PDF |
| Oracle® Identity Manager Connector Guide for Novell eDirectory Release 9.0.4 Part Number E10432-05 |
|
|
View PDF |
This chapter provides an overview of the updates made to the software and documentation for the Novell eDirectory connector in release 9.0.4.4.
The updates discussed in this chapter are divided into the following categories:
This section describes updates made to the connector software.
Documentation-Specific Updates
This section describes major changes made to this guide. These changes are not related to software updates.
The following sections discuss updates made from release 9.0.4 to the current release of the connector:
The following are software updates in release 9.0.4.1:
The eDirProv.jar file has been split into two files, eDirProv.jar and eDirRecon.jar. Corresponding changes have been made in the following sections:
The following are software updates in release 9.0.4.2:
From Oracle Identity Manager release 9.1.0 onward, the Administrative and User Console provides the Connector Installer feature. This feature can be used to automate the connector installation procedure.
See "Installing the Connector on Oracle Identity Manager Release 9.1.0 or Later" for details.
The following are issues resolved in release 9.0.4.3:
| Bug Number | Issue | Resolution |
|---|---|---|
| 8433456 | During trusted source reconciliation, two reconciliation events were created for each user record fetched from the target system. | This issue has been resolved. Only a single reconciliation event is created for each user record fetched from the target system.
The The See the section on configuring the IT resource for more information. The See "User Reconciliation Scheduled Task" for more information. |
The following are software updates in release 9.0.4.4:
Support for Provisioning Organizational Units, Groups, and Roles Using Multiple Object Classes
Support for Adding Custom Attributes for Trusted Source Reconciliation
By default, newly created organization units, groups, and roles on the target system are assigned to organization unit, group, and role object classes, respectively.
From this release onward, organization units, groups, and roles can be provisioned using multiple object classes.
See the "Adding Custom Object Classes for Provisioning" section for more information.
By default, during trusted source reconciliation, the connector reconciles only the attributes listed in the "Reconciled Xellerate User (OIM User) Fields" section. From this release onward, the connector enables you to add custom attributes for trusted source reconciliation.
See the "Adding Custom Attributes for Trusted Source Reconciliation" section for more information.
The following are issues resolved in release 9.0.4.4:
| Bug Number | Issue | Resolution |
|---|---|---|
| 5695644 | During a Create eDirectory Group provisioning operation, in the Organization Unit process form field, if you entered an organization unit that did not exist in the target system, then an error message was displayed that did not provide sufficient details to identify the cause of the error. |
This issue has been resolved. During a Create eDirectory Group provisioning operation, if you do not specify an organization unit that does not exist in the target system, then the following error message is displayed:
|
| 8583836 | A case-sensitive check was performed on the ReconMode attribute in the Code Key column of the Lookup.EDIR.Organization and Lookup.EDIR.UserGroup lookup definitions. If the case (uppercase or lowercase) of the ReconMode attribute did not match the case of the attribute name on the target system, then group and organization lookup reconciliation failed. |
This issue has been resolved. A case-sensitive check is not performed on the ReconMode attribute in the Code Key column of the Lookup.EDIR.Organization and Lookup.EDIR.UserGroup lookup definitions. |
| 8583865 | By default, during the Create User provisioning operation, the Organization DN process form field displayed the Regular value. If you continued with the provisioning operation without specifying the correct value in the Organization DN field, then the provisioning operation failed. The invalid naming exception was thrown. |
This issue has been resolved. The Organization DN field on the process form displays no value. Therefore, an appropriate value must be specified to proceed with provisioning operation. If no value is specified for this field, then the following error message is displayed:
|
| 8586122 | The status of the Delete User task was Rejected when the connector was configured for identity reconciliation (trusted source) mode. In addition, the status of the user remained at provisioned even after the corresponding OIM User was deleted. |
This issue has been resolved. After the Delete User operation, the status of the user changes to Revoked and Delete User task changes to Completed. |
| 8590100 | When the password of the OIM User was changed, the Update Password task was not triggered. | This issue has been resolved. The Update Password task is triggered when you change the password of an OIM User. |
| 8597067 | A naming exception was encountered if the User ID field contained a special character that was not supported by the target system. This exception did not provide sufficient details to identity the cause of the error. | This issue has been resolved. The following error message is displayed if the User ID field contains a special characters that are not supported by the target system:
|
The following sections discuss documentation-specific updates made from release 9.0.4 to the current release of the connector:
The following documentation-specific updates have been made in releases 9.0.4.1 and 9.0.4.2:
In the "Lookup Fields Reconciliation Scheduled Task" section, the description of the CodeKeyLTrimStr attribute has been modified.
In the "Configuring the Connector for Multiple Installations of the Target System" section, UD_EDIR_OU, UD_EDIR_RL, and UD_EDIR_GR have been added to the list of process forms that are created when you import the connector XML file.
There are no known issues associated with this release of the connector. Points that were earlier listed in the "Known Issues" chapter have been moved to the "Guidelines to Be Applied While Using the Connector" section.
The following documentation-specific updates have been made in release 9.0.4.3:
The "Configuring the Connector for Multiple Installations of the Target System" section has been removed from the "Configuring the Connector" chapter.
The following documentation-specific updates have been made in release 9.0.4.4:
A note has been added in the "Supported Functionality" section.
In the "Enabling Logging" section, all instances of the log4j.logger.XL_INTG.eDirectory= entry have been replaced with log4j.logger.XL_INTG.EDIRECTORY=.
The following sections have been added:
In the "Delete User Errors" section, text in the Solution column has been modified.
|
 Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
