Hi All,
We have a requirement where we need to implement threshold during account aggregation task.We need to terminate the task If identity creation is > 30. Thanks
@sureshbommareddy98 I am not aware of OOTB creation threshold. you need to monitor it programmatically using some rule like Creation Rule and then throw error to exit the task.
Let’s wait for other Sailors if they are aware of creation threshold.
It is not there out of the box. IdentityIQ has no built-in “max new identities” threshold on the aggregation task, so it needs a small customization.
can you try using Pre-iterate rule on the app.: Compare the incoming accounts against existing Links. If the count of new accounts is greater than 30, throw an exception. That aborts the aggregation before any identities are created.
There is no OOTB configuration in IIQ to stop account aggregation based on the number of new identities created.
You will need a small customization using a Pre-Iterate rule. You can compare the incoming accounts against existing Links and identify how many new identities would be created.
If the count exceeds 30, throw an exception to stop the aggregation.
This way, you can prevent unexpected identity creation during aggregation.
Hi @sureshbommareddy98 ,
As @kallajayaram mention you can do pre check for account aggregation in pre -Iterator rule, but there is limitation like if you using JDBC/webservice as your tourthsource application this is not feasible why because these applications don’t have pre-Iterator rule.
once you conform which tourthsource application currently you are useing
better you can use the creation/customization rule it will available in all applications and make logic below:
counter + throw exception
counter - mantain a simple counter on evey time new identity creation, increment the counter
throw exception - when counter exceeds 30+ throw a exception this cause the aggregation task to terminate
Optionally better- check box in aggregation task Only create links if they can be correlated to an existing identity.
let me know further querys.
I think there are more options for this requirement, depending what are exact details of it:
- Implement application Creation Rule where you count number of identities being created and then terminate the aggregation task if it exceeds defined threshold. The counter could be implemented by using in memory variable, e.g. use sailpoint.object.CustomGlobal static map, environment variable that is passed to the rule or your own Java static variable. This will work only for non-partitioned aggregations. If you use partitioning you will need to keep counter differently, e.g by using Custom object.
- Create clone of the application, and then implement CustomizationRule for the cloned application (both apps are pretty much the same, just differs with name and customization rule being defined). Then you define sequential task that first executes aggregation for cloned app (we can call it validation phase), and then executes real aggregation for the source app. The CustomizationRule defined on the “validation” app always returns null, so whatever is read by the connector is ignored and not reflected on the Identity. The rule only contains validation logic for the source data. Once validation task is completed it can be decided if real app aggregation can be safely executed or not. It is much more flexible approach than first option as it allows you first collect statistics on the entire aggregation data set and then decide if do aggregation or not.