Oracle® Identity Manager Connector Guide for RSA Authentication Manager Release 9.0.2 Part Number B32168-01 |
|
|
View PDF |
The following are known issues associated with this release of the connector:
RSA Authentication Manager APIs for extracting the group membership of user accounts are also exposed with the standard set, Sd_ListGroupMembership.
Although this API is not used with the XL OOTB released connector, if you intend to extend the OOTB connector to use the same API, then keep in mind the following limitation:
If there is a delimiter character (for example, a comma) in the default shell, then it would result in incorrect output from the API (which is comma separated).
Therefore, you must make the required changes to handle such exceptional cases.
While creating a user in RSA Authentication Manager, you must not enter special characters in the Default Login field. If you enter special characters in this field, then reconciliation would not work because Oracle Identity Manager does not support special characters in the User ID field.
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 locale 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.
The connector does not support the use of security certificates that contain non-English characters.