The following sections describe known issues and workarounds associated with this release of the connector:
The following are issues and workarounds associated with Oracle Identity Manager:
The following issue is observed while using the connector with Oracle Identity Manager 11g Release 2 BP04 (11.1.2.0.4):
Updating a child table does not work as expected. No provisioning task is triggered.
The fix for this bug is available in Oracle Identity Manager 11g Release 2 BP05 (11.1.2.0.5). This fix is also available as a one-off patch to be applied on Oracle Identity Manager 11g Release 2 BP04 (11.1.2.0.4), from ARU for bug 16053618.
After performing a trusted delete reconciliation operation, a user remains in provisioned status if the user is deleted from Oracle Identity Manager.
As a work around, run the target delete reconciliation scheduled job after running the trusted delete reconciliation task.
For any use case where identity is reconciled authoritatively from a target system to Oracle Identity Manager, and also account daily changes are provisioned from Oracle Identity Manager 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 job run. After the account reconciliation is completed, the scheduled job will convert the Account status to Revoked state. Eventually, the identity data maintained inside Oracle Identity Manager would look correct from operational as well as audit perspective.
If you revoke all the roles and privileges associated with a user from a target system and run target reconciliation, no event or log is generated. The roles and privileges are not revoked from Oracle Identity Manager.
There is no workaround available for this issue.
In Oracle and MySQL databases, With Grant Option in child data does not appear in the entitlements list in Oracle Identity Manager 11g Release 2 (11.1.2.0.0).
There is no workaround available for this issue. However, you can successfully perform a provisioning operation, even if the With Grant Option in child data does not appear in the entitlements list.
For Oracle Identity Manager hosted on a Microsoft Windows computer, installation fails if you try to install the connector again, for a different target system.
As a workaround, you must extract the connector bundle zip file again before installing the connector.
This issue has been fixed in Oracle Identity Manager release 11g R1 PS1 BP09 (11.1.1.5.9).
The following are issues and workarounds associated with the target system:
Creating a JDBC connection through Microsoft JDBC Driver 2.0, 3.0, 4.0 CTP 3, or jTDS 1.2.5 driver to a Microsoft SQL Server 2008 R2 database using JDK 1.6.0_29 results in an indefinite wait for a connection.
To work around this issue, use a version later than JDK 1.6.0_29.
MSSQL incremental reconciliation does not involve role updates. The stored procedure for receiving roles information does not have any timestamp or filter-based query support. Therefore, it is not possible to process role updates using incremental reconciliation in MSSQL.
There is no workaround available for this issue.
For the MySQL database, the connector does not provide a relevant error log when you try to provision a duplicate user. This issue is because of the behavior of the MySQL database.
There is no workaround available for this issue.
For the MySQL database, the connector does not support provisioning of privileges for the schema (information_schema and performance_schema). This issue occurs because a user (for example, root@localhost ) who is given ALL on *.* may not have the ALL privilege on the information_schema.* schema.
This is the behavior of the MySQL database.
There is no workaround available for this issue.