This chapter provides an overview of the updates made to the software and documentation for the Oracle E-Business User Management connector in release 9.0.4.3.
See Also:
The earlier release of this guide for information about updates that were new for that releaseThe 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 software updates:
The following are software updates in release 9.0.4.1_6728653:
Instead of using the apps target system account for connector operations, you can now use scripts provided in the connector installation package to create an account and assign the minimum required privileges to the account.
See "Configuring the Target System" for more information.
The following are issues resolved in release 9.0.4.1_6728653:
| Bug Number | Issue | Resolution |
|---|---|---|
| 6006892 and 6656960 | You had to use the APPS User with full privileges for connector operations. | You can now create a target system account for connector operations with the required privileges. Scripts have been provided in the connector installation package for creating this target system account. See "Configuring the Target System" for more information. |
| 6597512 | If you used release 11.5.10 of the target system with Oracle Database 10g, then the following exception was thrown during Update User provisioning operations:
|
This issue has been resolved. You can now use any combination of the supported target system and database releases. |
| 6436324 | The connector did not support the Change User Name provisioning operation. | This issue has been resolved. The connector now supports the Change User Name provisioning operation. |
| 6686927 | Names of some of the connector objects were not clear. | This issue has been resolved. Where required, names of the connector objects have been modified. |
| 6666957 | When you performed an Enable User provisioning operation, the Start Date of the user of user account on the target system is set to the current date and the end date is set to NULL. When you performed a Disable User operation, the Start Date of the user of user account on the target system remains the same and the end date is set to the current date. This is expected behavior.
However, the Start Date and End Date values on Oracle Identity Manager itself do not reflect the changes made on the target system. |
This issue has been resolved. During an Enable or Disable User provisioning operation, the Start Date and End Date on Oracle Identity Manager reflect the changes made on the target system. |
| 6337981 | The Password Expiration field of the target system is mapped to the Lifespan Type field of Oracle Identity Manager. During a Create User provisioning operation, the Lifespan Type field is set to None.
During an Update User provisioning operation, the value of the Password Expiration field set to the Access option automatically changed to |
This issue has been resolved. If the Lifespan Type field is set to None, then the Password Expiration field is also set to None. |
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 languages have been added to the list of supported languages:
Arabic
Japanese
See "Multilanguage Support" for more information.
The following are issues resolved in release 9.0.4.2:
| Bug Number | Issue | Resolution |
|---|---|---|
| 7271848 | If you changed the user password during a provisioning operation, then the password field on the target system was updated but the password_date field on the target system was not set to the system date. | This problem has been resolved. When you change the user password during a provisioning operation, the password_date field is set to the system date of the target system. |
The following are issues resolved in release 9.0.4.3:
| Bug Number | Issue | Resolution |
|---|---|---|
| 7175655 | During a provisioning operation, the password field was automatically updated if you updated any of the other process form fields. | This issue has been resolved. The password field is not automatically updated when you update any other process form field. |
The following sections discuss documentation-specific updates:
The "Target System Stored Procedures Used During Provisioning" section has been added.
In the "Known Issues" chapter, the following point has been added:
"This release of the connector does not support the addition of custom child table attributes for provisioning."
In the "Verifying Deployment Requirements" section, changes have been made in the "Target system" row.
From this release onward:
The minimum certified release of Oracle Identity Manager is release 9.1.0.1.
The minimum certified release of JDK is release 1.4.2.
See "Verifying Deployment Requirements" section for the complete listing of certified components.