Set up an Atlassian connector

Capabilities

Resource	Sync	Provision
Accounts
Workspaces
Groups

This connector can provision roles in Atlassian workspaces. Depending on your Atlassian implementation, not all roles may be available for all workspaces, and some roles can be only configured if the user meets certain requirements. The Atlassian connector is unable to predict whether a role will be available to a user before the role is requested, but the connector will show an error if a requested role cannot be provisioned.

Gather Atlassian credentials

Each setup method requires you to pass in credentials generated in Atlassian. Gather these credentials before you move on.

ImportantA user with the Org admin role in Atlassian must perform this task.

Create an organization API access token

Log into your Atlassian account.

Navigate to Organization Settings > API keys.

Click Create API key.

Select API key without scopes and set a Name and Expire Date, then click Create API key.

Review the key info and click Create API Key. The new organization API key is generated.

Carefully copy and save the API key and the organization ID. If the organization ID is not shown, you can look it up.

Optional: Request endpoints for provisioning support

If you want to provision workspace roles with the connector, you must raise an Atlassian Support ticket asking the Atlassian team to enable certain necessary endpoints on your tenant.

In the Atlassian Support Portal, log into your admin account for the organization you’re connecting and select Contact.

Make the following selections when prompted:

What can we help you with?: Technical issues and bugs
Which product is this for?: Select a cloud product you use, such as a JIRA instance

Click Raise a support request, and add your email to the “Include admin or billing/technical/end-customer contact, or additional participants on this ticket” field.

In the Summarize your issue box, enter: I need access to three Atlassian Administration Cloud API endpoints. The documentation states that access should be requested from the support team.

From the What is the impact to your business? drop-down, select Level 3.

In the Give us more details section, enter the following, replacing “<ATLASSIAN_ORGANIZATION_ID>” with your Organization ID:

I need access to the following endpoints of the Atlassian Administration Cloud API:
* Grant User Access: https://developer.atlassian.com/cloud/admin/organization/rest/api-group-directory/\#api-v1-orgs-orgid-users-userid-roles-assign-post
* Revoke User Access: https://developer.atlassian.com/cloud/admin/organization/rest/api-group-directory/\#api-v1-orgs-orgid-users-userid-roles-revoke-post
* Invite User to Org: https://developer.atlassian.com/cloud/admin/organization/rest/api-group-directory/\#api-v1-orgs-orgid-users-invite-post
I'm working with an API client and I need to be able to use these endpoints on my Atlassian organization.
My organization ID is: <ATLASSIAN_ORGANIZATION_ID>
Thanks in advance for your help!

Submit the request.

That’s it! Next, move on to the connector configuration instructions.

Configure the Atlassian connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Atlassian credentials generated by following the instructions above

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.

In ConductorOne, navigate to Admin > Connectors and click Add connector.

Search for Atlassian and click Add.

Choose how to set up the new Atlassian connector:

Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed. If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

Click Next.

Find the Settings area of the page and click Edit.

Paste the organization API access token into the Access token field.

Paste the organization ID into into the Organization ID field.

Click Save.

The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your Atlassian connector is now pulling access data into ConductorOne.

Follow these instructions to use the Atlassian connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Step 1: Configure the Atlassian connector

In ConductorOne, navigate to Connectors > Add connector.

Search for Baton and click Add.

Choose how to set up the new Atlassian connector:

Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

Click Next.

In the Settings area of the page, click Edit.

Click Rotate to generate a new Client ID and Secret. Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Atlassian connector deployment:

Secrets configuration

# baton-atlassian-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-atlassian-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Atlassian credentials
  BATON_API_TOKEN: <Atlassian organization API access token>
  BATON_ORG: <Atlassian org ID>

  # Optional: include if you want ConductorOne to provision access using this connector
  BATON_PROVISIONING: true

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-atlassian.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-atlassian
  labels:
    app: baton-atlassian
spec:
  selector:
    matchLabels:
      app: baton-atlassian
  template:
    metadata:
      labels:
        app: baton-atlassian
        baton: true
        baton-app: atlassian
    spec:
      containers:
      - name: baton-atlassian
        image: ghcr.io/conductorone/baton-atlassian:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-atlassian
        envFrom:
        - secretRef:
            name: baton-atlassian-secrets

Step 3: Deploy the connector

Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.

Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the Atlassian connector to. Atlassian data should be found on the Entitlements and Accounts tabs.

That’s it! Your Atlassian connector is now pulling access data into ConductorOne.

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

Set up an Atlassian connector

Capabilities

Gather Atlassian credentials

Create an organization API access token

Optional: Request endpoints for provisioning support

Configure the Atlassian connector

Step 1: Configure the Atlassian connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

​Capabilities

​Gather Atlassian credentials

​Create an organization API access token

​Optional: Request endpoints for provisioning support

​Configure the Atlassian connector

​Step 1: Configure the Atlassian connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Atlassian credentials

Create an organization API access token

Optional: Request endpoints for provisioning support

Configure the Atlassian connector

Step 1: Configure the Atlassian connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector