Folks,
I am seeing duplicate AD accounts being provisioned for several identities—each duplicate appears just seconds after the original. I’ve reviewed the configuration and can’t find a cause. Any ideas on what might be triggering this?
Here is one example:
As you can see, there is a gap of only 8 seconds between these two activities.
On the identity, here are the events
1.Duplicate Entitlement or Role Assignment
2.If the identity is aggregated from multiple sources and both are configured with provisioning capability, IdentityNow might trigger duplicate account
An update,
SailPoint determined it was caused by multiple aggregation jobs running concurrently, triggering accidental refresh, and causing account creation request. The issue was resolved by enabling a feature flag that prevents duplicate account creation.
Hello Sunny.
I’m experiencing the same issue. How did you fix it? Was the feature flag involved, or what exactly does it do?
Thanks in advance.
@gscalia
Create a support ticket for SailPoint team and let them do the RCA on your issue. If cause is same as mine, then they should be able to enable the feature flag in your tenant. Remember this is an internal feature flag to which only SailPoint has access.
Hope this helps.
