Hi,
In SailPoint IdentityIQ what is the retention policy for Access History Data. How long the Access History data is stored?
Regards,
Prashansa Rai
Hi,
In SailPoint IdentityIQ what is the retention policy for Access History Data. How long the Access History data is stored?
Regards,
Prashansa Rai
@Prash AFAIK there is no expiration because IIQ is using it to build an identity timeline since the identity came to IIQ till date.
Note: Found a fix?Help the community by marking the comment as solution. Feel free to react(
,
, etc.)with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.
Hi @neel193
Do you have the information about the recommended RAM size for IdentityIQ Access History Database as the Database sizing guideline document has the information about the space but could not find anything related to RAM size.
Thanks,
Prashansa Rai
@Prash There is no additional RAM configuration required. Access History module consumes more storage but from memory perspective no additional RAM is required. You can continue with current IIQ memory specifications and it should work.
I spoke to SP support awhile back and at that time there was no plan to add pruning capabilities to Access History, it was up to the customer to implement something. I believe the ideas portal has some requests for it.
Even if I can’t purge, I’d like to filter out what goes into Access History. I made a last login timestamp searchable and every time that updates IIQ thinks that’s a significant change to be added to the history. Also I have to remind auditors that the timestamp of the event is when the task “Dispatch Access History” ran, not the actual change.