The following are known issues associated with this release of the connector:
Bug 13979826
After performing a trusted delete reconciliation operation, a user remains in provisioned status if the user is deleted from Oracle Identity Manager (OIM).
As a work around, run the target delete reconciliation scheduled task after running the trusted delete reconciliation task.
For any use case where identity is reconciled authoritatively from a target system to OIM, and also account daily changes are provisioned from OIM back to the target system, this behavior will be observed.
The solution is to leverage on the existing infrastructure of account reconciliation and schedule it to run at the optimal frequency so that it follows trusted delete reconciliation scheduled task run. After the account reconciliation is completed, the scheduled task will convert the Account status to Revoked state. Eventually, the identity data maintained inside OIM would look correct from operational as well as audit perspective.
Bug 13975499
This issue applies to Oracle Identity Manager releases prior to 11.1.2. The request dataset provided with the connector does not contain the User Login field, which is usually fed directly from Oracle Identity Manager user profile to the process form using a prepopulate adapter.
To include the User Login field in request dataset, perform the following procedure:
Bug 13650341
During a provisioning operation, if the connector encounters a timeout error, an incorrect response message is displayed in the resource history of the scheduled task.
For example:
Response: CONNECTOR_EXCEPTION
Response Description: Unknown response received
Bug 13690646
After upgrading the connector, the parent form is not linked to the child form. As a work around, you must create a new version of the parent form and make it active.
Bug 13695758
If you update an encrypted basic configuration parameter such as loginUserPassword, other encrypted parameters such as passphrase and rbacRolePassword also appear to have been updated.