4 Known Issues

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

• To ensure that provisioning is completed successfully, you must specify either the role or profile in the field provided in the process form and then specify whether it is a role or profile. This is to activate the user on the SAP CUA master system.

• The connector can reconcile elements present in the SAP CUA master system only.

• The connection pool cannot be implemented because the current release of Oracle Identity Manager does not support it.

• Creation of a user on the SAP system involves running the Create User and Change Password functions in sequence. This event makes three RFC calls to the SAP system. The Create User RFC and Change Password RFC functions commit the transaction explicitly at the end of the call. This commit is enforced by the SAP architecture. This architecture constraint of SAP makes transactional maintenance between Create User and Change Password infeasible.

• When a user is created, the password specified is not allocated to the user. Later, the SAP system requires the user to specify the password again, which is assigned to the user at this stage. To prevent the occurrence of this event, when a user is created, the user is assigned a dummy password. After user creation, the Change Password function is run automatically. The password changes from the dummy password to the one entered by the user in the SAP User form in Oracle Identity Manager. This process is not visible to the user.

• When a user is created, the password is set only for the SAP CUA Master system, not the SAP CUA Child system.

• Password validation is not done in Oracle Identity Manager because the password rule is configurable on the SAP system.

• Suppose a user is created in SAP CUA and then locked. When this user is reconciled for the first time, the user may not get locked because linking in Oracle Identity Manager takes place in an asynchronous manner. This user is successfully locked during the next reconciliation run.

• Suppose a user is deleted from SAP CUA. During reconciliation, the user is deleted from Oracle Identity Manager. However, the Delete User function is also run and a message saying that the user does not exist on the target system is displayed. This message can be ignored.

• 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 SAP 4.7 or later, you cannot enter non-English letters in the E-mail Address field.

• The connector uses the JCO API that supports JDK 1.4 to communicate with SAP CUA. Oracle Identity Manager supports the Oracle Containers for J2EE (OC4J) release that works on JDK 1.5. Therefore, the connector does not support OC4J.