This chapter provides an overview of the updates made to the software and documentation for the Siebel User Management connector in release 9.0.4.15.
Note:
Release 9.0.4.15 of the connector comes after release 9.0.4.12. Release numbers from 9.0.4.13 and 9.0.4.14 have not been used.
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 software updates:
The following is a software update in release 9.0.4.1:
The xlSiebel.jar file has been split into two files, xlSiebel.jar and SiebelRecon.jar. Corresponding changes have been made in the following sections:
Section 2.1.1, "Files and Directories on the Installation Media"
Section 2.1.2, "Determining the Release Number of the Connector"
The following are issues resolved in release 9.0.4.1_6713023:
| Bug Number | Issue | Resolution |
|---|---|---|
|
6713023 |
User reconciliation and provisioning did not work due to connection failure. |
The issue has been resolved. |
The following are issues resolved in release 9.0.4.2:
| Bug Number | Issue | Resolution |
|---|---|---|
|
7014401 |
Time zone values that you set during provisioning was not displayed on the target system. |
This issue has been resolved. The time zone value is correctly stored during provisioning. |
The following are software updates implemented in release 9.0.4.3:
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 Section 2.2.1, "Installing the Connector on Oracle Identity Manager Release 9.1.0.x or Release 11.1.1" for details.
The following are issues resolved in release 9.0.4.4:
| Bug Number | Issue | Resolution |
|---|---|---|
|
7308907 |
Incremental reconciliation failed if the target system database was set to any time zone other than GMT. For example, if the time zone of the target system database was set to GMT+08:00, then incremental reconciliation would fail. |
This issue has been resolved. The SiebelDatabaseTimeZone attribute has been added to the Siebel Recon scheduled task. You can use this attribute to specify the time zone of the target system database. See Section 3.4.4, "User Reconciliation Scheduled Task" for more information about the SiebelDatabaseTimeZone attribute. |
The following are issues resolved in release 9.0.4.5:
| Bug Number | Issue | Resolution |
|---|---|---|
|
7308907 |
The connector uses the time stamp stored in the TimeStamp IT resource parameter to identify target system records that must be reconciled. However, daylight savings time was not taken into account. |
This issue has been resolved. The DayLightSaving attribute has been added to the SiebelRecon task. You use this attribute to specify the time (in minutes) that must be added to the time stamp. Sample value: With this sample value, 60 minutes are added to the time stamp stored in the TimeStamp parameter, and the new time stamp is used to identify records that have been created or modified after the last reconciliation run. Default value: Note: The SiebelDatabaseTimeZone attribute of the SiebelRecon scheduled task has been renamed to SiebelServerTimeZone. |
|
7163582 |
The following issue was observed when the target system was Siebel 8.0: In a provisioning operation, if you tried to assign a responsibility to a user who had no responsibilities, then the connection exception was encountered. |
This issue has been resolved. In a provisioning operation, you can now assign responsibilities to a user who does not have any responsibilities. |
|
7561587 |
You could not set a primary responsibility to a user through a provisioning operation. |
This issue has been resolved. You can now use the PrimaryResponsibility lookup field to set a primary responsibility during provisioning. See Also: Bug 7703095 in the "Known Issues" chapter for information about an issue related to this feature. |
|
6847114 |
On the target system, if a position name was used across more than one division, then only one occurrence of the position name was reconciled into the Lookup.Siebel.Position lookup definition. |
This issue has been resolved. Position names are reconciled according to their unique IDs on the target system. The following are sample entries from the Lookup.Siebel.Position lookup definition: Code Key1: Decode1: Code Key2: Decode2: |
|
7668306 |
If a responsibility name reconciled from the target system contained a special character, then that responsibility could not be assigned to a user through a provisioning operation. |
This issue has been resolved. Responsibilities whose names contain special characters, except the single quotation mark character ('), can now be assigned to user through provisioning. Note: A responsibility whose name contains the single quotation mark (') character cannot be assigned to a user through provisioning. This is because the target system cannot search for a responsibility name if it contains a single quotation mark. |
|
7667566 |
An exception was encountered if you deleted a user's position through a provisioning operation. |
This issue has been resolved. You can delete a user's responsibility through provisioning. |
|
7673332 |
A user's status was Inactive even when one or more responsibilities were assigned to the user through provisioning. |
This issue has been resolved. If a user has no responsibilities assigned, then the status of the user is set to Inactive. If you assign responsibilities to the user through provisioning, then the status is changed to Active. |
The following are software updates implemented in release 9.0.4.6:
From this release onward, the connector supports Siebel 8.1.1. This is mentioned in Section 1.1, "Certified Components."
The following table describes issues resolved in release 9.0.4.6:
| Bug Number | Issue | Resolution |
|---|---|---|
|
8223113 |
When you assign a primary position to an employee through a provisioning operation on Oracle Identity Manager, the change is correctly reflected in the Administration – User module on the target system. However, in the Administration – Group module, the check box designating that the position is primary for that particular employee remains deselected. |
This issue has been resolved. The relationship between an employee and a primary position is correctly shown in the Administration – Group module. The "Assigning a Position to Users" section has been removed from the connector guide. |
The following table describes issues resolved in release 9.0.4.7:
| Bug Number | Issue | Resolution |
|---|---|---|
|
7579522 |
When you assigned a primary position to an employee through a provisioning operation on Oracle Identity Manager, the employee became the primary user for the position. When you assigned the same primary position to another employee, this employee became the new primary user for the position. In this way, the primary user of the position kept changing with each assignment of the position. |
This issue has been resolved. The first employee to whom the position is assigned remains the primary user of the position. |
The following table describes issues resolved in release 9.0.4.8:
| Bug Number | Issue | Resolution |
|---|---|---|
|
8362522 |
The connector did not work correctly if Oracle Identity Manager and Oracle Access Manager both used the same object manager (CommunicationsObjMgr_enu). The following error was encountered during password operations:
|
This issue has been resolved. The connector functions as expected even if Oracle Identity Manager and Oracle Access Manager are using the same object manager. The SSO and Trusted Token parameters have been added in the IT resource definition. |
The following are software updates implemented in release 9.0.4.9:
Support for Adding Single-Valued and Multivalued Attributes for Reconciliation and Provisioning
Addition of the Configuration and Constants Lookup Definitions
From this release onward, you can add single-valued and multivalued attributes for target resource reconciliation and provisioning. See Chapter 4, "Extending the Functionality of the Connector" for more information.
The following lookup definitions have been added in this release:
Lookup.Configuration.Siebel
This lookup definition holds connector configuration entries that are used during reconciliation and provisioning.
Lookup.Siebel.Constants
This lookup definition stores values that are used internally by the connector. The connector development team can use this lookup definition to make minor configuration changes in the connector.
From this release onward, you can configure transformation of data during reconciliation.
See Section 1.4.6, "Support for Transformation of Data During Reconciliation" for more information.
The following table describes issues resolved in release 9.0.4.9:
| Bug Number | Issue | Resolution |
|---|---|---|
|
8734174 |
The logging feature did not record some exceptions. |
This issue has been resolved. All exceptions are now recorded by the logging feature. |
The following are software updates implemented in release 9.0.4.12:
From this release onward, the connector can be installed and used on Oracle Identity Manager 11g release 1 (11.1.1). Where applicable, instructions specific to this Oracle Identity Manager release have been added in the guide.
See Section 1.1, "Certified Components" for the full list of certified Oracle Identity Manager releases.
From this release onward, the connector provides support for request-based provisioning on Oracle Identity Manager 11g release 1 (11.1.1).
See Section 3.6.2, "Request-Based Provisioning" for more information.
The following are software updates implemented in release 9.0.4.15:
From this release onward, the connector provides support for importing a request dataset XML file into Oracle Identity Manager by using the Deployment Manager on Oracle Identity Manager 11g release 1 (11.1.1).
The installation media of this release includes a request dataset file, SiebelConnectorRequestDatasets.xml, which is available in the xml directory.
See Section 2.3.1.8.1, "Importing Request Datasets Using Deployment Manager" for more information.
The following table describes issues resolved in release 9.0.4.15:
| Bug Number | Issue | Resolution |
|---|---|---|
|
11871430 |
When you provision a Siebel resource to a user having special characters, an error was encountered. |
This issue has been resolved. Resources can be provisioned to users having special characters. |
|
11665189 |
During a full reconciliation operation, if there was a special character in a user name, an error was encountered. |
This issue has been resolved. Users having special characters in their user names are reconciled without any errors. |
|
10373871 |
Reconciliation of a new Siebel user to Oracle Identity Manager failed if the user record did not exist in Oracle Identity Manager. |
This issue has been resolved. New Siebel users can be reconciled to Oracle Identity Manager. |
|
9432044 |
When adding a secondary responsibility to a user, an error was encountered. |
This issue has been resolved. A secondary responsibility can be added to a user. |
|
9358528 |
After upgrading Siebel connector from release 9.0.4.8, an error was encountered during provisioning. |
This issue has been resolved. Upgrading the connector from release 9.0.4.12 to this release prevents the error caused during provisioning. |
|
9238731 |
During a provisioning operation, using custom process forms failed because the form names were included in the software code. |
This issue has been resolved. The names of the custom process forms use the Lookup.Siebel.Constants lookup definitions. |
|
12403295 |
When a user of type User is provisioned with a value for work phone, the WorkPhone field was not updated. |
This issue has been resolved. The WorkPhone field is updated when provisioning to users of type User. |
|
12403335 |
When a user of type User is provisioned with a value for primary responsibility, the PrimaryResponsibility field was not updated. |
This issue has been resolved. The PrimaryResponsibility field is updated when provisioning to users of type User. |
|
12380304 |
During a full trusted source reconciliation operation, an error was encountered for users of type User if the TimeStamp IT resource parameter is empty. |
This issue has been resolved. The full trusted source reconciliation operation for users of type User is successful. |
|
12374876 |
During target resource reconciliation, the UserType and the SiebelServerTimeZone attribute values of a user were not reconciled. |
This issue has been resolved. The the UserType and the SiebelServerTimeZone attribute values of a user are reconciled. |
|
12369295 |
When a primary responsibility was added, the user status in the Siebel process form was not set to ACTIVE. |
This issue has been resolved. The user status is set to ACTIVE after adding a primary responsibility. |
|
12365104 |
When a trusted source reconciliation scheduled task was run, if the IsTrusted attribute was set to True, the task also triggered a target system reconciliation event. |
This issue has been resolved. The trusted source reconciliation scheduled task does not trigger a target system reconciliation event. |
|
12365135 |
During a provisioning operation, setting a value for the Position field was mandatory for users of type User. |
This issue has been resolved. The users of type User can be provisioned without setting a value for the Position field. |
|
12561788 |
After a provisioning operation, if the Siebel process form was customized and the Position field was made optional, the user was not found on the target system. |
This issue has been resolved. A user can be provisioned with customized Siebel process form. |
|
12542513 |
For a user with primary and child responsibilities, if the child responsibilities were deleted, the user status was inactive. |
This issue has been resolved. For a user with primary responsibility, if the child responsibilities are deleted, the user status is ACTIVE. |
The following sections discuss documentation-specific updates:
The following documentation-specific updates have been made in the guide from release 9.0.4.1 through 9.0.4.6:
The external code files for Siebel 7.6, 7.7, and 7.9 have been documented in the following sections:
In Section 1.6.1, "User Attributes for Target Resource Reconciliation and Provisioning," the following fields have been added:
Extension
HomePhone
WorkPhone
MPosition
Title
The Phone and PersonalTitle fields have been removed from the list.
In Section 3.4.2, "Limited Reconciliation":
All occurrences of givenname have been replaced with First Name.
All occurrences of sn have been replaced with Last Name.
In the "Known Issues" chapter, limitations of the target system have been separated from the known issues of the connector.
The "Creating the Target System User Account for Connector Operations" has been added.
In the "Extending the Functionality of the Connector" chapter, the "Configuring the Connector for Multiple Installations of the Target System" section has been removed. This feature is not supported by default.
The following documentation-specific updates have been made in the guide for release 9.0.4.8:
The following sections have been added:
In Section 1.2, "Certified Languages,", Arabic has been added to the list of languages that the connector supports.
In Section 1.1, "Certified Components," changes have been made in the "Target systems" row.
Major changes have been made in the structure of the guide. The objective of these changes is to improve the usability of the guide.
The following documentation-specific updates have been made for release 9.0.4.10:
The following changes have been made in Chapter 1, "About the Connector":
Some of the sections have been rearranged.
Section 1.8, "Roadmap for Deploying and Using the Connector" has been added.
The following documentation-specific updates have been made for release 9.0.4.12:
Information about the Position and Responsibility resource object fields has been removed from Section 1.6.1, "User Attributes for Target Resource Reconciliation and Provisioning."
The following sections have been added:
The following documentation-specific updates have been made for release 9.0.4.15:
In Section 2.2.1.2, "Configuring the IT Resource," the descriptions of some parameters have been modified.
In Section 2.3.1.7, "Configuring Trusted Source Reconciliation," the path to locate and import xml files have been updated.
In Section 5.1, "Running Test Cases," the xlLogger.jar file has been removed from the list.
Section 2.2.2, "Installing the Connector on Oracle Identity Manager Release 9.0.1 Through 9.0.3.x" has been removed as this connector is no longer certified for Oracle Identity Manager release 9.0.1 through 9.0.3.x.