SoD Violations Don't Match In OIM And OAACG Due to Truncated Data in OAACG.
(Doc ID 2419016.1)
Last updated on APRIL 22, 2019
Applies to:Identity Manager - Version 18.104.22.168.0 to 22.214.171.124.190328 [Release 11g]
Information in this document applies to any platform.
OIM configured with EBS UM connector and SOD check is configured on OAACG for conflicting responsibilities. On raising request for 2 roles which are conflicting , GRC DB shows more number of violations than shown from OIM console.
1. Set up a violation criteria in OAACG.
2. Configure EBS UM connector and EBS OAACG IT connectors and resources.
3. Request for 2 responsibilities that would match the violation criteria in OAACG.
4. Submit the request .
5. Check from OAACG and OIM for number of violations reported for these requests and number of violations are different.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!