8 Oracle Identity Management Integration
Notes for this release include information about supported integrations.
8.1 Features Not Supported in Release 12.2.1.4.0
Oracle Identity Management does not support the following integration features in this release:
- Upgrading OAM-OIG integrated deployment is not supported in 12c (12.2.1.4.0). OAM-OIG integration is supported only for fresh installations of OAM and OIG.
-
For all directory types (OUD, OID, and AD) the following reconciliations are not supported:
-
User delete full and incremental reconciliation.
-
Reconciliation of deleted roles that have user members or child roles.
-
-
For Active Directory type, Role hierarchy full and incremental reconciliation is not supported.
-
If LDAP directory is used as a target in customer's setup, you cannot use it for OAM-OIG integration. It is not supported out-of-box and must be handled as one-off.
-
Reservation container is not supported in a connector-based OAM-OIG integration.
8.2 Features Not Supported in Release 12.2.1.4.0 (BP02)
Oracle Identity Management does not support the following integration features in this release after applying the OAM bundle patch 12.2.1.4.200327 or the OIM bundle patch 12.2.1.4.200505:
-
If LDAP directory is used as a target in customer's setup, you cannot use it for OAM-OIG integration. It is not supported out-of-box and must be handled as one-off.
-
Reservation container is not supported in a connector-based OAM-OIG integration.
8.3 Oracle Identity Management Integration Issues and Workarounds
Use OIG as a primary source for managing Users and Roles.
Perform deletion of users, or role related changes such as memberships and hierarchy in OIG and not directly against the directory.
The following are the known limitations for the OIG-OAM integration:
-
Group names must be unique in target LDAP for SSO-integrated setup.
-
Orchestration-Provisioning Compensation will not be performed by any of the LDAP account, role, user membership, and role hierarchy post process handlers.