Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 33 additions & 2 deletions baton/atlassian.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,12 +10,14 @@ sidebarTitle: "Atlassian"

| Resource | Sync | Provision |
| :--- | :--- | :--- |
| Accounts | <Icon icon="square-check" iconType="solid" color="#65DE23"/> | |
| Accounts | <Icon icon="square-check" iconType="solid" color="#65DE23"/> | <Icon icon="square-check" iconType="solid" color="#65DE23"/> |
| Workspaces | <Icon icon="square-check" iconType="solid" color="#65DE23"/> | <Icon icon="square-check" iconType="solid" color="#65DE23"/> |
| Groups | <Icon icon="square-check" iconType="solid" color="#65DE23"/> | |

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 Atlassian connector supports [automatic account provisioning](/product/admin/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.

## Gather Atlassian credentials

Each setup method requires you to pass in credentials generated in Atlassian. Gather these credentials before you move on.
Expand Down Expand Up @@ -50,6 +52,28 @@ A user with the **Org admin** role in Atlassian must perform this task.
</Step>
</Steps>

### Optional: Gather SCIM credentials for account provisioning

If you plan to use account provisioning to create new users, you'll need SCIM API credentials.

<Steps>
<Step>
Log into [your Atlassian account](https://admin.atlassian.com/).
</Step>
<Step>
Navigate to **Security** > **User Security** > **Identity Providers**.
</Step>
<Step>
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`)
</Step>
<Step>
Carefully copy and save both values. You'll need them to configure account provisioning.
</Step>
</Steps>

### 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.
Expand Down Expand Up @@ -137,6 +161,9 @@ If you want to provision workspace roles with the connector, you must raise an A
Paste the organization ID into into the **Organization ID** field.
</Step>
<Step>
**Optional.** If using account provisioning, paste the SCIM token and SCIM base URL into the relevant fields.
</Step>
<Step>
Click **Save**.
</Step>
<Step>
Expand Down Expand Up @@ -206,13 +233,17 @@ 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

# Optional: include for account provisioning (creating new users)
BATON_SCIM_TOKEN: <Atlassian SCIM token>
BATON_SCIM_BASE_URL: <Atlassian SCIM base URL>
```

See the connector's README or run `--help` to see all available configuration flags and environment variables.
Expand Down
2 changes: 1 addition & 1 deletion baton/capabilities.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ og:description: "A quick reference for how each connector can be set up and what
| [ArgoCD](/baton/argo-cd) | <Icon icon="plug" /> | <Icon icon="key" /> <Icon icon="user" /> | <svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" style={{display: 'inline-block', verticalAlign: 'middle'}}><rect x="3" y="11" width="18" height="11" rx="2" ry="2"/><path d="M7 11V7a5 5 0 0 1 10 0v4"/></svg> |
| [Artifactory](/baton/artifactory) | <Icon icon="cloud" /> <Icon icon="plug" /> | | |
| [Asana](/baton/asana) | <Icon icon="cloud" /> <Icon icon="plug" /> | <Icon icon="key" /> <Icon icon="user" /> | |
| [Atlassian](/baton/atlassian) | <Icon icon="cloud" /> <Icon icon="plug" /> | | |
| [Atlassian](/baton/atlassian) | <Icon icon="cloud" /> <Icon icon="plug" /> | <Icon icon="key" /> <Icon icon="user" /> | |
| [Auth0](/baton/auth0) | <Icon icon="cloud" /> <Icon icon="plug" /> | <Icon icon="key" /> | |
| [Avalara](/baton/avalara) | <Icon icon="cloud" /> <Icon icon="plug" /> | | |
| [AWS v1](/baton/v1/aws) | <Icon icon="cloud" /> | <Icon icon="key" /> | |
Expand Down