SoD Check for Cloned EBS Connector Uses Incorrect OAACG IT Resource (Doc ID 2416429.1)

Last updated on AUGUST 30, 2023

Applies to:

Purpose

There are 2 connectors - EBS User Management out of the box and cloned one called Cloned EBS

Issue: SoD check for Cloned resource is somehow using out of the box "OAACG-ITRes" IT resource which comes withe EBS connector instead of the one created for the cloned connector (Cloned OAACG-ITRes).

Documentation followed:  OIM guide 27.10.1: https://docs.oracle.com/cd/E21764_01/doc.1111/e14309/segduties.htm#OMDEV3439 but it does not mention is scenario:

Other observations: If one change the "Source Datastore Name" in the "OAACG-ITRes" IT resource used by EBS connector to point to datastore for Cloned for example: ClonedUAT instead of EBSUAT , SoD check for Cloned works correctly. But for cloned Resource, one is using cloned Cloned OAACG ITRes not the "OAACG-ITRes" IT resource which does not work correctly.

So the issue is how to make the cloned Cloned OAACG ITRes work for Cloned instead of out of the box OAACG-ITRes and has this scenario of using the SAME OAACG instance target for 2 connector (ebs and cloned ebs connector) with 2 OAAGC IT Resources has everything same except for "Source Datastore Name"been tested before and certified to work?

Details