We have disconnected systems (using flat file connector) and service desk for provisioning (Atlassian Jira). When an access request is made for an new entitlement, a ticket is logged. When the jira ticket is closed it marks it as provisioned and adds the basic information to the account in SailPoint. If we request more access, or change the lifecycle state to inactive before the aggregration is run, it creates a duplicate task for the entitlement request which was closed.
Since this is disconnected the aggregration will happen very infrequently.
This seems to be because it is not ‘closing the loop’ that access has been provisioned until the aggregation has run. Is there a configuration setting to treat the status of the ticket as access has been provisioned?
Or is there an option to make SailPoint ISC not create another provisioning task / ticket for a previously completed access request when a refresh happens.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.