|Oracle® Identity Manager Connector Guide for BMC Remedy User Management
|PDF · Mobi · ePub|
The following are known issues associated with this release of the connector:
Some Asian languages use multibyte character sets. If the character limit for the fields in the target system is specified in bytes, then the number of Asian-language characters that you can enter in a particular field may be less than the number of English-language characters that you can enter in the same field. The following example illustrates this limitation:
Suppose you can enter 50 characters of English in the User Last Name field of the target system. If you were using the Japanese language and if the character limit for the target system fields were specified in bytes, then you would not be able to enter more than 25 characters in the same field.
In a non-English environment, some of the text on the Administrative and User Console might appear in English because entries for these text items have not been added in the resource bundles.
To work around this issue, you can create and add entries for these items in the resource bundle that you want to use. See one of the following guides for more information:
For Oracle Identity Manager 9.1.0.x:
Oracle Identity Manager Globalization Guide
For Oracle Identity Manager release 11.1.1:
Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager
When you create entries, you must copy the key for each entry from the resource bundle for English.
The following issue is observed during trusted source reconciliation:
If a user is marked as Deleted on the target system and if that user has not been reconciled earlier in Oracle Identity Manager, then the user is created in the Enabled state on Oracle Identity Manager at the end of the reconciliation run.
This problem is automatically resolved at the end of the next reconciliation run. At that time, the status of the user in Oracle Identity Manager is set to Disabled.