Atlassian and its Suite integration

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hi Community!

I have to integrate the Atlassia Suite into Identity Security Cloud, I see many connectors available to my purposes but I can’t understand which covers best my requirements.
The Atlassian Suite to integrate is composed by the following applications:

  1. Jira
  2. Jira Service Management
  3. Confluence
  4. BitBucket

In the Identity Security Cloud Connectors page I can see many options available, let me list them below:

  1. Jira Service Management - Three connectors are available:
    ○ Atlassian Cloud Jira Service Management
    ○ Atlassian Data Center Jira Service Management
    ○ Atlassian Server Jira Service Management
  2. The entire Atlassian Suite (SaaS) with the Supported Managed Systems of Jira, Jira Service Management and Confluence. The only only left is BitBucket.

I appreciate your experience in the field to help understand which of these connectors should be used and for which purposes.

  1. Why would I choose a dedicated “Jira Service Management” connector over the generic “Atlassian Suite (SaaS)” connector?
  2. In case I would need for a dedicated “Jira Service Management” connector, which are the differences between the 3 listed above?
  3. By integrating the whole Atlassin Suite, would it be in charge of Atlassian to provision accounts and entitlements to BitBucket or should be SailPoint ISC to perform these operations?
  4. Please note that I can’t find any connector to maange BitBucket. How would it be possible to integrate BitBucket in SailPoint ISC? Would you recommend a Web Services connector or is the integration implicit within the Atlassian Suite?

Thank you for sharing your information!

2

  1. Jira Service Management is used for opening and closing Jira cases. You can use it as an enhancement for your flat file sources. If someone requests access in a flat file source, it would then open a ticket in Jira. Usually there is extra licensing costs involved with the SDIM connectors like Jira Service Management.

  2. Just depends on where you are hosting your Jira Service Management system. If it is the cloud version, select Atlassian Cloud Jira Service Management. etc.

  3. Unfortunately the Atlassian connectors cannot manage BitBucket. This is an Atlassian limitation not Sailpoint. If you look in the Atlassian forums, people have been asking for this enhancement for atleast 3 years. So you will need to figure out a manual process for creating BitBucket accounts, if you setup Jira Service Management, you could have that create tickets to have the BitBucket accounts setup.

  4. In my experience, the BitBucket APIs do not contain enough endpoints to effectively create a Web Services or SAAS Connector. If you figure out a way, please share it.

3

Thank you @Carlatto!
All clear about the (sad) BitBucket, but just one more clarification on the Jira connectors.

Since we have at least 3 different connectors (Cloud, Data and Server), each satisfies a different Jira application based on where it’s deployed.
Could you provide just one example each for when it’s necessary to use the “Data” and when the “Server” connectors?

4

We don’t use Jira Service Management. Looking at the connectors, it appears “Server” is no longer supported by Atlassian. I would assume “Data Center” should be used if you are hosting Atlassian on-premise, and “Cloud” should be used if you use Atlassian Cloud.

5

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.