Oracle® Identity Manager Connector Guide for UNIX Telnet Release 9.0.1 Part Number B31141-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 would get 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 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 provisioning, the data in the User Defined form fields must not contain the shell prompt character. As there is a variation in shell prompt character based on the relevant target Unix Server, it should be checked in the target.
During reconciliation with the trusted option set to YES
in the IT Resource, the value for the Shadow Mirror File
task 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.
During provisioning, the maximum permitted date value for account expiry is 31/12/2099.
After configuring an IT Resource for a Telnet user account and then directly provisioning 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.