5 Known Issues and Limitations

This chapter is divided into the following sections:

• Section 5.1, "Known Issues"

• Section 5.2, "Connector Limitations Related to Features of the Target System"

5.1 Known Issues

The following is a known issue associated with this release of the connector:

• Bug 7207232

  Some Asian languages use multibyte character sets. If the character limit for fields on 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 point:

  Suppose you can enter 50 characters of English in the User Last Name field of the target system. If you have configured the target system for the Japanese language, then you would not be able to enter more than 25 characters in the same field.

  See Section 4.3, "Modifying Field Lengths on the Process Form" for information about working around this issue.

5.2 Connector Limitations Related to Features of the Target System

The following are connector limitations related to features of the target system:

• The SPML UME API does not return records for which the Last Modified Date value is greater than a specified date. Therefore, the connector cannot support incremental reconciliation.

• Request-based provisioning is not supported. Because provisioning operations are routed through the Compliant User Provisioning module, the request-based provisioning feature of that module makes the feature in the connector redundant.

• Configurable batched reconciliation is not supported. The connector performs batched reconciliation implicitly when it first fetches user IDs whose records must be reconciled and then fetches the records.