Oracle® Identity Manager Connector Guide for SAP CUA, Release 9.0.1 Part Number B31134-01 |
|
|
View PDF |
The following are known issues associated with this release of the connector:
To ensure that the provisio ning completes 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 a user on the SAP CUA Master system.
During reconciliation, due to a bug in Oracle Identity Manager release 8.2, any insertion of data into the child tables causes provisioning tasks to be triggered. This tries to put the same information back into the target system. This causes performance degradation during bulk reconciliation.
The connector can reconcile elements present in the SAP CUA master system only.
The first step after deploying the connector must be to perform lookup reconciliation. Else you cannot perform provision tasks.
The connection pool implementation is not feasible because of lack of current Oracle Identity Manager architecture support.
Creation of a user on the SAP system involves running the Create User and Change Password use cases in a 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 eliminate the occurrence of this event, when a new user is created, the user is assigned a dummy password and after user creation the Change Password event is called 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 transparent to the end user.
When a user is created, the password is set only for the Master system, not the Child system.
Password validation is not done in Oracle Identity Manager because the password rule is configurable on the SAP system.