requiresPeriodicRefresh not triggering after daily ISC Identity Refresh

SailPoint Human Fabric (SHF) SHF Discussion and Questions
,
21

Stretching this topic a bit more…

So, it is clear that the identity refresh didn’t happen because my identity is “INACTIVE_LONG_TERM”.

However, now I just realized I have a situation that actually WORKS, but shouldn’t…

So, I have 2 “termination” LCS:

  1. Terminated
  2. Postterminated30days

Once we got termination conditions, identity goes to LCS “terminated”, which is INACTIVE_LONG_TERM.

After 30 days of the termination, it goes to LCS “postterminated30days”, also INACTIVE_LONG_TERM.

This process has been working perfectly for months.

But… if I don’t have more identity refreshes with INACTIVE_LONG_TERM, how could this process be working??? I mean, nothing changes in the identity after termination, postterminated30days is just a calculation based on “now” and the termination date. No requiresPeriodicRefresh set!

22

At what time of day did it do the terminated to postterminated30days. Was it on a refresh schedule or related to an auth source aggregation?

23

Aggregations happens 4x a day, so active to terminated can happen after any of those aggregations.
I never paid attention on postterminated30days, I will check some identities to see if detect any pattern.

24

Well, it makes things a bit strange:

There is no hour pattern, the shift to postterminated30days can happen at any time from what I have seen, and it happens nicely after 30 days, which suggest some daily validation is taking place. :exploding_head: