Identity Audit Violations Stuck In Expired Status
(Doc ID 2215730.1)
Last updated on FEBRUARY 28, 2019
Applies to:Identity Manager - Version 184.108.40.206.0 to 220.127.116.11.170117 [Release 11g]
Information in this document applies to any platform.
You've configured an expiration for the IdentityAuditRemediationTask in the IdentityAuditRemediation composite (or your custom remediation composite). But you observe that once an identity audit violation goes to an expired status, it does not get reassigned to the remediator the next time the scan definition is run. As a result, the remediator can never take any action on the violation in the future, and in fact, the violation may go unreported so no one is aware of it.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!