Hi,
In JDBC provisioning rule, I have a logic to Check if you provisioning modify account request has attribute request for attribute : bsv. [sub logic to query the table and get the corresponding value for BSV], If result is null, then remove attribute request from the plan.
But even though I remove attribute request from the plan, I still see the sailpoint audit events.
Hi @chandramohan27 , it’s expected if the plan is modified within the jdbc provisioning rule unless it’s done within the Before Provisioning rule.
Hi @chandramohan27,
You cannot alter the plan with a JDBC provisioning rule. It works more like an after rule, where the plan is fed to the JDBC rule and the rule processes what’s there in the plan.
If you need to alter the plan, you will need to modify it through a cloud rule - Before provisioning rule.
But in your case, you should be able to apply the logic to calculate the attributes in the plan and then process the required items according to what’s there in the plan.
Is there an option to remove the attribute request from the plan using a standard Before provisioning rule. I want to remove that attributeRequest from the Plan if attributeRequest > 1 and attributeRequests contains attribute.name = ''department"
Hi @chandramohan27,
No, you can’t remove the attributeRequest with a services standard BP rule.
You can consider setting up the logic in your JDBC rule to ignore the operations when the attribute request name is “department”.
I think this should work.
Yes, But the problem is Ignoring the operation still produces an SailPoint Audit events which is a false positive.
You will need to create a custom before provisioning rule to achieve this.