Can a connector have 2 different provisioning strategies in SailPoint IIQ?

[Shivaleela (Shivaleela Bathini)]

Hello Team, Greeting!

We’re looking for a feasibility on the below ask, appreciate your insights on same.

Can there be a possibility for a single connector to have different provisioning strategies.
For example: one entitlement request should create a service now ticket whereas the other entitlement should go for a direct provisioning according to the connector used .

Much appreciated if anyone can provide us some knowledge here.

Thanks,
Shivaleela.

[SaidurgaMallela]

Hi @Shivaleela

Yes, in SailPoint IIQ, it is possible to use different provisioning strategies for entitlements within the same connector.

You can do this by using a BeforeProvisioning rule. In this rule, you can check which entitlement is being requested, and then:

• For certain entitlements, modify the provisioning plan to create a ServiceNow ticket.
• For other entitlements, allow the default direct provisioning to continue.

The rule gives you full control to inspect and change the provisioning plan before IIQ processes it.

So yes, with the right logic in the BeforeProvisioning rule, you can handle both ServiceNow and direct provisioning in parallel within the same application.

[Shivaleela (Shivaleela Bathini)]

Thanks much @SaidurgaMallela , I’ve tried to initiate a SNOW ticket process from before provisioning rule, its working as expected.
One must need to ensure some checks that manually removing the attributes from provisioning plan so that flow will not go into direct provisioning flow/operations OR throwing a customized warning for users as this access request can never be completed unless we close it.