Post-Processor Used for User Profile Auditing

Auditing 6-9

6.3.4 Archival

User Profile audit data growth is based on the setting of the audit levels, and the growth can be significant in most of the deployments. There is also a requirement to clean or archive the old user profile audit data to accommodate future growth. You can use Audit Archival and Purge Utility to meet these requirements. See Using the Audit Archival and Purge Utility in the Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager for detailed information about this utility.

6.4 Role Profile Auditing

Role profile audits cover changes to role profile attributes, role administrators, and direct subroles. This section discusses the following topic: ■ Data Collected for Audits

6.4.1 Data Collected for Audits

Unlike user auditing, an independent audit level is not defined for role profile auditing. Instead, the audit levels defined for user profile auditing are used for role profile auditing. Role profile auditing takes place only if the audit level defined for user profile audit level is Membership or a level higher than that. By default, user profile auditing is enabled and the audit level is set to Resource Form when you install Oracle Identity Manager. As a result, role profile auditing is also enabled by default because the default audit level for user profile audit is Resource Form, which is higher than Membership. This section discusses the following topics: ■ Capture and Archiving of Role Profile Audit Data ■ Storage of Snapshots ■ Trigger for Taking Snapshots

6.4.1.1 Capture and Archiving of Role Profile Audit Data

Each time a role profile changes, Oracle Identity Manager takes a snapshot of the role profile and stores the snapshot in an audit table in the database. Note: ■ The UPA_UD_FORMS and UPA_UD_FORMFIELDS tables together store the audit trail of changes to the users account profile in a de-normalized format. These tables can be used in various audit-related reports. ■ The UPA_UD_FORMS and UPA_UD_FORMFIELDS tables will be populated only if the XL.EnableExceptionReports system property is set to TRUE. For more information about this property, see System Properties in Oracle Identity Manager in the Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager.