The standard behavior of SailPoint ISC is that it creates a ticket per source. If the role has 2 entitlement from Source A (JIRA Connector A) and 1 entitlement from Source B (JIRA Connector B), then two tickets are created in JIRA with the details about source entitlements:
- Ticket 1 → JIRA Connector A - entitlement 1, entitlement 2
- Ticket 2 → JIRA Connector B - entitlement 3
We need to adjust this process to our needs, and create a ticket pro entitlement. This is important, because depends on the entitlements values, the ticket will be assigned to the different teams in JIRA.
I made some research and found the information that in our case the modification of beforeProvisioingRule won’t work. We also cannot modify LCM Provisioning Workflow as in IIQ, because it’s not available to modify in ISC. I have also the idea to create the workflow with trigger Access Request Decision and try to modify the plan there → split the plan into the list of plans with only one Attribute Request. My problem is, that I’m not sure how I could do that using the available input and if in the end we will have the information about the status of JIRA Ticket per plan and if the account activity will be visible in SailPoint.
Do you have any idea how we can achieve it?