This chapter provides an overview of the updates made to the software and documentation for the UNIX Telnet 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 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 are software updates in release 9.0.4.2:
In Chapter 5, "Testing and Troubleshooting," the following attributes have been added to the list of testing utility attributes:
passwdMirrorFilePath: This parameter is used to specify the passwd mirror file path for reconciliation.
shadowMirrorFilePath: This parameter is used to specify the shadow mirror file path for reconciliation.
targetDateFormat: This parameter is used to specify the date format of the target UNIX computer.
The action attribute now supports additional parameters. The values can be any one of the following:
CONNECT
CREATE
CHANGEPASSWORD
MODIFY
DELETE
DISABLE
ENABLE
ENABLETRUSTED (only for HP-UX trusted mode)
Corresponding changes have been made in the following sections:
Supported Functionality on page 1-3
The following are the other software changes made in this release:
In the Section 2.5.4, "Enabling Logging", the name of the adapter for this connector has been changed from ADAPTERS.TELNETSSH to OIMCP.TELNETSSH.
In the "Compiling Adapters" section, the SSH updateHomeDir adapter has been added to the list of adapters.
In the IT resource definition, the following parameters have been removed:
Login Prompt
Password Prompt
Target Locale
Supported Character Encoding (en_US) – Target
The following scheduled task attributes have been converted into IT resource parameters:
Passwd Mirror File/User Mirror File
Shadow Mirror File
Target Date Format
The following table lists issues resolved from release 9.0.4.1 to this release of the connector:
| Bug Number | Issue | Resolution |
|---|---|---|
|
6375896 |
Target resource reconciliation threw exceptions when users were reconciled from Linux using a SUDO admin user. |
Target resource reconciliation issues related to Linux used in the SUDO mode have been resolved. |
|
6609731 |
The |
The |
|
6642345 |
The connection retry feature of the connector was not working correctly. |
Issues related to the connection retry feature have been resolved. |
|
6680047 |
If a connection retry attempt was made, then previous sessions were not released and new sessions were established each time. |
Connectivity issues related to session leakage have been resolved. |
|
6728741 |
An incorrect response was received from the connector if the username value was greater than 8 characters and the Create Home directory check box was selected. |
The responses received from the connector have been corrected. |
|
6742869 |
A user could not be provisioned if there were spaces in value of the GECOS field. |
Spaces are now allowed in the GECOS field. |
|
6766705 and 6801405 |
The status of the resource object stayed at |
Issues related to the resource object status and response during provisioning have been resolved. |
|
6786399 |
The connector was unable to handle responses from target systems running a non-English locale. |
Responses from target systems running a non-English locale are now handled correctly. |
|
6801537 |
During reconciliation, temporary files were created in the |
During reconciliation, temporary files are now created in the |
|
6837471 |
A user could not be provisioned with spaces in the values of any of the user attributes. |
Spaces are now allowed in many of the user attributes. |
|
5180204 |
On AIX computers, the connector was not able to reconcile a large number of records. |
Issues related to the reconciliation of a large number of users on AIX have been resolved. |
|
5502324 |
Date format parsing errors were encountered during reconciliation. |
The date format parsing error that was encountered during the user reconciliation has been resolved. |
|
5503100 |
The message displayed when the user name had multibyte characters during a Create User provisioning operation was incorrect. |
The message displayed when the user name has multibyte characters during a Create User provisioning operation has been modified. |
|
5647992 |
On Linux, Solaris, and AIX computers, the Home Directory attribute could not be updated. |
The Home Directory attribute is updated correctly on Linux, Solaris, and AIX targets. |
|
5180227 |
The IT Resources contained two redundant parameters, |
The |
|
6604117 |
The Password and Confirm Password fields on the process form were not encrypted. |
The Password and Confirm Password fields have been modified to accept encrypted values. |
|
6310073 |
During provisioning, if user creation on the target system failed at some stage, then the user was not cleaned up from the target system although the status of the resource was |
During provisioning, if the user is not created properly on the target, then the user is deleted from the target system and the resource object status is set to |
The following updates have been made in release 9.0.4.3:
The Primary Group Name field on the process form has been converted into a lookup field. During a provisioning operation, you can now select a primary group instead of entering the name of the group. The TelnetSSHGroupLookupReconTask scheduled task has been added to reconcile (synchronize) the values in the lookup definition with primary group names in the target system.
The name of the target resource reconciliation scheduled task has been changed from Telnet User Non Trusted Reconciliation task to Telnet Target Resource User Reconciliation Task.
The level of detail has been increased for data logged when you set the log level to DEBUG. With this log level, it is now easier to track down the cause of an error recorded in the log file.
In Chapter 6, "Known Issues," the following point has been added:
Bug 7172629
For a particular provisioning operation or reconciliation run, if the connector fails to establish a connection with the target system, then subsequent retries to establish a connection would fail. The number of retries is determined by the value specified for the MaxRetry IT resource parameter.
After the cause of the connection failure is corrected, the connection attempt is successful for the next provisioning operation or reconciliation run.
The following table lists issues resolved from release 9.0.4.1 to this release of the connector:
| Bug Number | Issue | Resolution |
|---|---|---|
|
7121688 |
On AIX 5.3, the |
This issue has been resolved. You can now update the User Login attribute through a provisioning operation. Note: The Update User Login provisioning operation is not supported by default on AIX 4.x and 5.1. However, if you upgrade these versions of AIX to support the useradd, usermod, and userdel commands, then you can perform the Update User Login provisioning operation. |
|
7143486 |
If a reconciliation run ended in an exception, then the connection with the target system was not closed. |
This issue has been resolved. The connection with the target system is closed even if a reconciliation run ends in an exception. |
The following is a software update in release 9.0.4.4:
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.4, "Installing the Connector on Oracle Identity Manager Release 9.1.0.1 or Release 11.1.1" for details.
The following are software updates in release 9.0.4.5:
In the IT resource, the Whether SUDO Admin Mode parameter has been renamed to Sudo Or RBAC.
See Chapter 2, "Deploying the Connector" for information about these parameters.
The following table lists issues resolved in release 9.0.4.5:
| Bug Number | Issue | Resolution |
|---|---|---|
|
5503263 |
The "Create Home Directory" field is a check box on the Administrative and User Console. If you selected this check box, the numeral 1 was displayed on the page that summarizes input you provide during provisioning operations. |
The check box has been changed to a radio button. If you select the "Create Home Directory" option, then the word "Yes" is displayed on the page that summarizes input. If you do not select the option, then the word "No" is displayed. |
|
7172629 |
The |
If the connection fails, then the connector attempts to reestablish a connection up to the number of times specified by the |
|
7210292 |
The home directory of a Telnet account was not deleted when you revoked the account. |
The home directory of a Telnet account is deleted when you revoke the account. |
|
7225692 |
To stop a scheduled task, you use the Stop Execution option in the Design Console. This option did not work in earlier releases. |
You can now use the Stop Execution option to stop scheduled tasks. Note: When you stop a batched reconciliation run, reconciliation stops at the end of the current batch. |
|
7237286 |
A Telnet account could not be provisioned on the Linux target system. |
You can now provision Telnet accounts on the Linux target system. |
The following table lists issues resolved in release 9.0.4.6:
| Bug Number | Issue | Resolution |
|---|---|---|
|
7503701 |
The target system does not allow you to delete a user who is logged in to the system. This is expected behavior. However, even when the target system did not allow the deletion of a user, the status of the user (resource) on Oracle Identity Manager was changed to Deleted (Revoked). |
This issue has been resolved. If the target system does not allow the deletion of a user, then an appropriate message is displayed as the outcome of the Delete User provisioning operation. The item describing this issue has been removed from the Chapter 6, "Known Issues". |
The following are software updates in release 9.0.4.7:
From this release onward, the connector adds supports for Oracle Enterprise Linux 5.2 as a target system.
This target system version is mentioned in "Verifying Deployment Requirements" on page 2-1.
The following table lists issues resolved in release 9.0.4.7:
| Bug Number | Issue | Resolution |
|---|---|---|
|
7520249 |
During reconciliation, you could not transform values of the target system field before they were stored in Oracle Identity Manager. |
This issue has been resolved. You can now transform the values of the target system fields before they are stored in Oracle Identity Manager. See the "Transforming Data Reconciled Into Oracle Identity Manager" section for more information. |
|
7563415 |
During reconciliation, the Group Name field was reconciled as a number and not as the exact name because it was stored directly as the group ID in the target system. |
This issue has been resolved. During reconciliation, the exact name of the Group Name field is reconciled. |
|
8396795 |
During connector deployment, the lib/xliTenet.jar file on the installation media was not automatically copied into the OIM_HOME/xellerate/ScheduleTask directory. |
This issue has been resolved. The lib/xliTelnet.jar file is now automatically copied to the OIM_HOME/xellerate/ScheduleTask directory. |
The following table lists issues resolved in release 9.0.4.11:
| Bug Number | Issue | Resolution |
|---|---|---|
|
9100879 |
The Delete User provisioning operation did not work. |
This issue has been resolved. The Delete User provisioning operation now works correctly. |
|
9195323 |
The Create User provisioning operation failed when it was retried. |
This issue has been resolved. The Create User provisioning operation can be retried. |
The following are the software updates 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.
From this release onward, the connector adds support for IBM AIX 5L Version 6.1 as the target system.
See Section 1.1, "Certified Components" for the full list of certified target systems.
From this release onward, the connector can reconcile user account status information from the target system.
The following table lists issues resolved in release 9.0.4.12:
| Bug Number | Issue | Resolution |
|---|---|---|
|
7374688 |
Reconciliation of user records in the sudo mode failed because the connector attempted to run a shell. |
This issue has been resolved. |
|
9295029 |
When an update task failed, the status of the corresponding process task adapters changed from |
This issue has been resolved. The status of the process task adapters do not change when the corresponding update task fails. |
|
9611960 |
When performing a Create User provisioning operation on AIX, the group name must be specified as the value of the Primary Group Name lookup field. However, instead of displaying group names, the Primary Group Name lookup field displayed group IDs. The happened due to the following reason: After performing lookup field synchronization by running the TelnetSSHGroupLookupReconTask scheduled task, the Code Key column of the UD_Lookup_SSH_PrimaryGroupNames lookup definition contained the group IDs, and the Decode column contained the group names. |
This issue has been resolved. After you perform lookup field synchronization, the connector now reconciles group names into the Code Key column, and group IDs into the Decode column of the UD_Lookup_SSH_PrimaryGroupNames lookup definition. Therefore, for AIX and the other target systems, the connector passes the group name instead of the group ID. |
|
9611211 |
The Confirm Password field on the process form required users to enter their passwords 2 times. |
The Confirm Password field has been removed from the process form. |
The following are software updates implemented in release 9.0.4.15:
From this release onward, the connector adds support for HP-UX version 11iv3 (11.31) as the target system.
See Section 1.1, "Certified Components", for the full list of certified target systems.
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, TelnetConnectorRequestDatasets.xml, which is available in the xml directory.
See Section 2.5.5.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 |
|---|---|---|
|
11737066 |
When running the SSH User Target Resource Reconciliation Task, if the number of users to be reconciled is greater than the batch size, an exception is thrown. |
This issue has been resolved. The reconciliation task runs successfully for multiple batches. |
|
7498112 |
The connector did not support HP-UX11I V2,V3 as a target resource. |
.This issue has been resolved. HP-UX11I V2,V3 is now supported as a target resource. |
The following sections discuss documentation-specific updates:
The following documentation-specific updates have been made in releases 9.0.4.1 through 9.0.4.4:
In Section 2.3.2, "Configuration Steps for AIX," the command to create a user mirror file on the server has been changed.
In Section 2.3.3, "Configuration Steps for HP-UX," the procedure has been modified.
In the "Compiling Adapters" section on page 3-9, the list of adapters has been updated.
Changes have been made in the following sections:
Adding Custom Attributes for Reconciliation
Adding Custom Attributes for Provisioning
In Chapter 6, "Known Issues," the following items have been added:
A reconciliation run stops if the scheduled task code encounters target system user data containing the character or characters that are same as the shell prompt of the target system.
From Chapter 6, "Known Issues," the following item has been removed:
When you configure an IT resource for a Telnet user account and then directly provision it to a user, the Create User Task function is rejected. The user account is not created on the target system. The following message is displayed:
"TELNET_USERCREATION_NOTCONNECTED_FAIL not able to connect successfully to the Target System Server".
The following are documentation-specific updates in release 9.0.4.5:
In Chapter 2, "Deploying the Connector," the Protocol parameter has been added in the table that describes the IT resource parameters.
Bug numbers have been added for all the known issues.
The following guidelines have been moved from Chapter 6, "Known Issues" to other parts of this guide:
This connector does not support logins that differ by case only. It also requires all logins to be distinct considering that their values are automatically converted to uppercase by Oracle Identity Manager.
For example, the user logins jdoe and JDOE would be considered different on a UNIX server. However, from Oracle Identity Manager, the input would always be passed as JDOE, because user ID values are stored only in uppercase in Oracle Identity Manager.
During provisioning, the maximum permitted date value for account expiry is 31/12/2099.
The following point has been removed from Chapter 6, "Known Issues":
The Update Secondary Group Names and Update User Login functions do not work simultaneously.
At some places in this guide, corrections have been made to address some documentation issues.
The following are documentation-specific updates in release 9.0.4.7:
Changes have been made in the following sections:
Scheduled Tasks for Trusted Source and Target Resource Reconciliation
Section 4.4, "Transforming Data Reconciled Into Oracle Identity Manager" has been added.
The following point has been removed from Chapter 6, "Known Issues":
During reconciliation, the Group Name field is reconciled as a number and not as the exact name because it is stored directly as the group ID in the target system.
The following appendixes have been added:
The following are documentation-specific updates in release 9.0.4.11:
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" for the complete listing of certified components
Major changes have been made to the structure of the guide. The objective of these changes is to synchronize the guide with the changes made to the connector and to improve the usability of the information provided by the guide.
The following is documentation-specific updates in release 9.0.4.15:
In Chapter 2, "Deploying the Connector", Table 2-1, "Files and DIrectories on the Installation Media" has been updated.
In Chapter 2, "Deploying the Connector", Section 2.4.2, "Copying the sshfactory.jar File" has been added.
In Chapter 2, "Deploying the Connector", Section 2.4.4, "Copying the Configuration Files" has been added.
In Chapter 2, "Deploying the Connector", Section 2.5.5.1, "Importing Request Datasets Using Deployment Manager" has been modified.
In Section 2.4.3, "Configuring the IT Resource", the table values have been updated.
In Chapter 3, "Using the Connector", Table 3-2, "Attributes of the User Reconciliation Scheduled Tasks" has been updated.
In Chapter 3, "Using the Connector", Section 3.5, "Guidelines on Performing Provisioning Operations" has been updated.
In Chapter 4, "Extending the Functionality of the Connector," Section 4.4, "Transforming Data Reconciled Into Oracle Identity Manager" has been modified.
In Chapter 5, "Testing and Troubleshooting," expiry date format has been added in the table.
In Chapter 5, "Testing and Troubleshooting," a note on testing utility has been added.
The directory path in step 4 of section Section 2.5.1, "Configuring the Target System As a Trusted Source" has been changed.