Identity Audit Violations Stuck In Expired Status (Doc ID 2215730.1)

Last updated on MARCH 08, 2017

Applies to:

Identity Manager - Version 11.1.2.3.0 to 11.1.2.3.161018 [Release 11g]
Information in this document applies to any platform.

Symptoms

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. 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms