| Oracle® Identity Manager Connector Guide for UNIX Telnet Release 9.0.3 Part Number B32375-01 |
|
|
View PDF |
| Oracle® Identity Manager Connector Guide for UNIX Telnet Release 9.0.3 Part Number B32375-01 |
|
|
View PDF |
The following are known issues associated with this release of the connector:
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 in 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 data in the User Defined form fields must not contain the shell prompt character. Because there is a variation in shell prompt character depending on the target UNIX server, it should be checked in the target system.
During provisioning, the maximum permitted date value for account expiry is 31/12/2099.
Suppose that a user on the UNIX server is disabled. If the Set Password function is run on this user account, then the account is automatically reenabled.
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.
During reconciliation, the user login field is successfully reconciled only if the user ID does not exceed 32 characters.
During reconciliation with the trusted option set to YES in the IT resource, the value for the Shadow Mirror File attribute must not be NULL or blank.
While creating an IT resource, the user name provided for Admin UserId must be that of an active user in the target system. This means that the user must not be locked or disabled.
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".
On AIX 5.2, while providing data in the GECOS field, ensure that there are no spaces. If there are spaces in this field, then the Update User Login function would not work.
The Update Secondary Group Name and Update User Login functions do not work simultaneously.
The Update Inactive Days function does not work on AIX 5.2.
Oracle Identity Manager does not support special characters in the User ID field on HP-UX, Solaris, and Linux target systems. If a user were created with special characters in the User Login field, then reconciliation would not work.
The Enable User function is not supported by the HP-UX (trusted) target system.
This release of the connector does not support all the shell types that are available on various operating systems. For information about the supported shell types, refer to the table at the end of the "Step 1: Verifying Deployment Requirements" section.
The entry of multibyte characters is not supported in some fields. Refer to Appendix A for more information about this known issue.
