| Oracle® Identity Manager Connector Guide for JD Edwards EnterpriseOne Release 9.0.3 Part Number B32448-02 |
|
|
View PDF |
| Oracle® Identity Manager Connector Guide for JD Edwards EnterpriseOne Release 9.0.3 Part Number B32448-02 |
|
|
View PDF |
The following are known issues associated with this release of the connector:
The target system does not accept a user ID that is longer than 10 characters. During provisioning, if you specify a user ID that is longer than 10 characters, then the first 10 characters are used to create the user ID on the target system.
This limitation also applies to the password that you specify for the new user.
While reconciling users from the target system, the User ID value is used to populate the First Name and Last Name fields of the Xellerate User account in Oracle Identity Manager.
This connector does not support secure connection between Oracle Identity Manager and the target system because the interoperability solution used in building the connector does not support this type of connection.
The only way to secure communication between Oracle Identity Manager and the target system is to place both on a secure network.
Linking in Oracle Identity Manager is asynchronous. If a user is created in the target JD Edwards system and then disabled in the JD Edwards system, then that user might not be disabled in Oracle Identity Manager in the first reconciliation run. The user will be disabled in Oracle Identity Manager in the second reconciliation run.
The Brazilian Portuguese language has not been supported for this release of the connector.
While creating a user in a provisioning operation, if you specify the login credentials in a multibyte language (for example, Japanese or Korean), then the user account may not be correctly created on the target system. The user will not be able to log in to the target system.
The following sample scenario illustrates this problem:
While installing the operating system on the target system server, suppose you had selected the English language for installation. Now, you are using a language pack for the Japanese language that you want to use on that server. As mentioned earlier, on this target system, the login credentials of newly created user accounts will not work.
However, suppose you had selected the Japanese language while installing the operating system on the target system server. You do not need to use the Japanese language pack on this server. On a target system installed on this server, a user would be able to log in using user credentials created on Oracle Identity Manager.
