Why should I use Sailpoint's SCIM connector instead of its direct Jira/Confluence API connector?

[Alex van Vucht]

Sailpoint IdentityIQ supports managing users and groups directly through the users and groups API endpoints in Jira/Confluence Cloud. This is trivial to set up, and it reports back directly all accounts in the site. It also doesn't cost Atlassian Guard licenses.

Sailpoint's SCIM connector is difficult to set up and doesn't aggregate accounts that already exist in cloud. Why should I use the SCIM connector instead? What does SCIM user provisioning offer over directly provisioning users through the Jira/Confluence Cloud API?

[Marc -Devoteam-]

Hi @Alex van Vucht 

Welcome to the community.

Based on my knowledge SCIM is required for provisioning.

Provisioning options on the provisioning API you can make changes to users and groups.

The sailpoint integration can set more attributes and other options, like multiple group entitlements.

Via the API this has to be done per user.