Detecting Identity Refresh in a Before Provisioning Rule

[mingsiewang (Ang Ming Siew)]

Hi experts,

Does anyone know how I can detect an identity refresh in a Before Provisioning Rule?

We have a business requirement to manipulate certain data during a modify operation - but this should only be done during aggregation, not during an identity refresh (possibly triggered by attribute sync), hence I would like to check if its possible to detect it in my BP rule?

[gogubapu (bapu gogu)]

Hi @mingsiewang,

Check Processing Identity Data - SailPoint Identity Services Documentation. i think this will helps to you.

Thank you.

[mingsiewang (Ang Ming Siew)]

Hi Bapu,

The documentation doesn’t cover anything about detecting it in the Before Provisioning rule though.

[dylanfoggan]

Hi @mingsiewang ,

You would typically need to modify the Workflow associated with the identity refresh.

The ISC processing for the Identity Refresh is designed to map the account and identity data / Trigger the update account operation. This being said I wouldn’t recommend you attempt to modify that in a rule.

Thanks,

[gogubapu (bapu gogu)]

Hi @mingsiewang,

I think we can’t detect that identity refresh task using before provisioning rule and workflows as well.

Thank You.

[mingsiewang (Ang Ming Siew)]

Hi Bapu & Dylan,

Thank you for your responses, I believe we can’t detect identity refresh in our BP rule, we’ll find an alternative then.

Appreciate the responses!