Delta Aggregation

In Full Aggregation, the timestamp for account aggregation is stored in the Application object, which is used by the Delta Aggregation feature to aggregate updated data into IdentityIQ. This timestamp is updated after each account delta aggregation.

Note
The IdentityIQ for Okta connector supports delta aggregation for accounts only.

By default, delta aggregation fetches changes to accounts' user profile attributes and entitlements. In order to aggregate the complete list of attributes present in a schema, add the following entry key to the application XML via the Identity IQ Debug page:

<entry key="enableFullROinDelta"; value="true">

The delta for Okta user profile attributes is populated from the users API by comparing the timestamp of the last successful account aggregation against the last updated attribute.

To detect entitlement changes and deleted users, the data is populated from the logs API by comparing the timestamp of the last successful account aggregation against the published attribute.

Note
Log data older than 90 days is not returned in accordance with Okta's Data Retention Policy. This means that any data change done prior to 90 days of the last successful account aggregation timestamp aren't captured. Therefore a full account aggregation will be required to capture the change.

For all delta aggregations after applying 8.1 Patch 4, 8.2, or 8.0 Patch 5, the logs API is considered regardless of the application definition.