5 Known Issues

The following are known issues associated with this release of the connector:

• 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.

• The connector does not support the use of security certificates that contain non-English characters.

• 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.

• The following limitation applies to the use of the Japanese, Simplified Chinese, Traditional Chinese, Korean, and French languages:

  RSA APIs do not support certain characters of the character sets of these languages. The provisioning or reconciliation operation fails if any of the field values submitted during the operation contains any one of the unsupported characters at the start of the field value. However, the operation does not fail if unsupported characters appear at any place other than the start of the field value.

  See Also:

  For more information about the characters not supported in provisioning and reconciliation, refer to the metalink note 421232.1 in the metalink Web site at https://metalink.oracle.com.