How Access History Works
History events related to Access History objects are constructed and published to the history writer API through a scheduled event or ad hoc service. You can configure how frequently Access History runs, but the default is once per day.
Each history event describes all of the information about a single IdentityIQ access history object (e.g., identity, role, etc.) in a map structure. A history event can also reference other historical objects.
Data extract reads objects in IdentityIQ, formats them into JSON, writes them to a message bus, then the history store reads them from the message bus and persists them into the Access History database.
The Access History user interface lets you search the database. There are also APIs that the UI can use to query against the database, processing Identity, Role, Identity Entitlements, Certifications, Identity Requests, Managed Attributes, Capabilities, Accounts, Workgroups, and Policy Violations.
The system identifies duplicates so they are not processed twice and can distinguish between initial events and change events. Unchanged objects are not processed.
To use this functionality, you need to complete the following:
1. Setting Up Access History Database and Tables
2. Setting Up Access History Task