5 Known Issues and Limitations

This chapter is divided into the following sections:

5.1 Known Issues

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

Bug 7207232

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.
Bug 9268577

If there are a large number users or tokens to be reconciled during full reconciliation, then the InvalidSessionException exception might be encountered.

See Section 3.3, "Guidelines on Performing Reconciliation" for information about a workaround to this issue.

The following are connector limitations arising from features of the target system:

In the earlier release of the target system, the next token code mode could be set through an administrative API. RSA Authentication Manager 7.1 does not support this feature.
In RSA Authentication Manager 7.1, a group assignment change for a user updates neither the group record nor the user record. Therefore, incremental reconciliation does not bring the updated user record into Oracle Identity Manager.
On the target system, the Lock User and Unlock User operations can be performed only through the application of lockout policies defined on the target system. The connector does not provide a UI option for these features.
The connector does not support fetching of the emergency access token code if the token is lost