Skip to main content

Capabilities

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. The connector can also add and remove users from Atlassian groups. Group membership provisioning uses the organization API key and does not require the extra endpoint access described below. Groups synced from an identity provider (SCIM) cannot be modified this way; manage those in the identity provider instead. The Atlassian connector supports automatic account provisioning via SCIM API. New users are created in the directory without passwords. If a managed Atlassian account already exists for the specified email address, the user will be linked to that existing account. The connector also supports account deprovisioning. When C1 deprovisions a user, the connector deletes their Atlassian account, which removes their access to every Atlassian product in the organization. Atlassian keeps the account deactivated for a 14-day grace period before the deletion is permanent. Deprovisioning only works for managed accounts (accounts on a domain your organization has verified) and uses the organization API key. During the 14-day grace period, the deleted account stays on the app’s Accounts tab in C1 with the status For Deletion; it is not removed until Atlassian finishes the deletion. Atlassian can take several minutes to report the new status, so the first syncs after a successful deprovision may still show the account as active. If you deprovision an account that is not managed by your organization, Atlassian rejects the request with 403 Forbidden: Caller must be a verified org admin of targeted account or be the targeted account, and C1 falls back to manual deprovisioning.

Account status

C1 sets each account’s status from the status Atlassian reports for the user in your organization: If Atlassian reports any other status, C1 marks the account Enabled only when both the account and the membership are active, Disabled when either one is inactive, closed, suspended or missing a membership, and leaves the status unspecified when it can’t tell.

Connector actions

Connector actions are custom capabilities that extend C1 automations with app-specific operations. disable_user and enable_user suspend and restore access to this organization only. deactivate_user and activate_user act on the whole Atlassian account, blocking or restoring access to every Atlassian app in any organization. They only work for managed accounts (accounts on a domain your organization has verified). For accounts provisioned from an identity provider, including accounts this connector creates through SCIM account provisioning, Atlassian requires deactivating them in the identity provider. For those accounts, use disable_user and enable_user instead. The two pairs are independent: activate_user does not lift an organization suspension, and enable_user does not reactivate a deactivated account. To fully restore a user who may be either or both, run activate_user and then enable_user. In our tests, both succeeded on accounts already in the target state. A user restored with only activate_user while still suspended, or with only enable_user while still deactivated, can show as enabled in C1 until the next sync but still has no access. Neither pair restores an account pending deletion (for_deletion): activate_user fails with a 409. To keep that account, cancel its deletion in Atlassian within the 14-day grace period.

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

2
Navigate to Organization Settings > API keys.
3
Click Create API key.
4
Select API key without scopes and set a Name and Expire Date, then click Create API key.
5
Review the key info and click Create API Key. The new organization API key is generated.
6
Carefully copy and save the API key and the organization ID. If the organization ID is not shown, you can look it up.

Optional: Gather SCIM credentials for account provisioning

If you plan to use account provisioning to create new users, you’ll need SCIM API credentials.
2
Navigate to Security > User Security > Identity Providers.
3
Configure an identity provider with provisioning enabled. After configuring it, you will get a window with both:
  • The SCIM token (BATON_SCIM_TOKEN)
  • The SCIM base URL (BATON_SCIM_BASE_URL)
4
Carefully copy and save both values. You’ll need them to configure account provisioning.

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.
1
In the Atlassian Support Portal, log into your admin account for the organization you’re connecting and select Contact.
2
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
3
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.
4
In the Summarize your issue box, enter: I need access to two Atlassian Administration Cloud API endpoints. The documentation states that access should be requested from the support team.
5
From the What is the impact to your business? drop-down, select Level 3.
6
In the Give us more details section, enter the following, replacing “<ATLASSIAN_ORGANIZATION_ID>” with your Organization ID:
7
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 C1
  • Access to the set of Atlassian credentials generated by following the instructions above
Follow these instructions to use a built-in, no-code connector hosted by C1.
1
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for Atlassian and click Add.
3
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
4
Set the connector’s Name and, optionally, a Description.
5
Click the pencil icon next to Owners to choose who can configure and manage this connector.
6
Click Add. The connector is created and its configuration page opens.
7
Find the Settings area of the page and click Edit.
8
Paste the organization API access token into the Access token field.
9
Paste the organization ID into into the Organization ID field.
10
Optional. If using account provisioning, paste the SCIM token and SCIM base URL into the relevant fields.
11
Click Save.
12
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 C1.