- 21 Nov 2023
- 4 Minutes to read
- Print
- DarkLight
- PDF
Atlassian Cloud
- Updated on 21 Nov 2023
- 4 Minutes to read
- Print
- DarkLight
- PDF
You need to have an Atlassian Access subscription to enable this connector.
This guide will teach you how to set up the connector between Atlassian Cloud and Clarity Security.
Estimated time to complete: 10 minutes
If you run into any problems, please contact your support team or support@claritysecurity.io.
Supported Connector Capabilties
Below are the capabilities supported by the connector at this time.
Method | Supported |
---|---|
Provision User | No |
List Groups, Policies, and Roles | No |
Add User to Groups, Policies, and Roles | No |
Remove User from Groups, Policies, and Roles | No |
Deactivate User | No |
Delete User | No |
How to Setup the Connector
Step 1: Head to https://developer.atlassian.com and sign in
Step 2: Once signed in, click on the user profile picture in the top right corner and choose Developer Console
Step 3: Click the Create button above the list of API connections (this list may be empty) and in the sub menu choose “OAuth 2.0 Integration”
Step 4: Give a name to the new API connection, make sure this is descriptive enough in the event you have future API connections (or to distinguish from pre-existing ones). Check the box agreeing to the Atlassian Developer terms, and then click Create
Step 5: Now that your connection is created, you should be automatically loaded into the Settings page for the new connector. Click on the “Permissions” button on the left side
Step 6: On the permissions page, click Add (this changes to Configure after you make changes) next to the line stating Jira API
Step 7: Click Edit Scopes under the Platform REST API section, ensure you are under Classic not Granular scopes
Step 8: Click the checkboxes for “Manage Jira global settings” and “View user profiles”, and then click Save
Step 9: On the permissions page, click Add (this changes to Configure after you make changes) next to the line stating Confluence API
Step 10: Click Edit Scopes under the Platform REST API section, ensure you are under Classic not Granular scopes
Step 11: Click the checkboxes for “Manage Confluence Space Details”, “Manage Confluence Global Settings”, "Read User", "Read User Groups", "Create, Remove, and Update User Groups" and then click Save
Step 12: On the left-hand side click Authorization (Should be directly below the Permissions button from Step 5). Click the “Add” button on the line for OAuth 2.0 (3LO)
Step 13: Fill out the “Callback URL” for your integration using the following link. You must replace “YOUR_DOMAIN” with the first part of your Clarity Security URL
https://YOUR_DOMAIN.claritysecurity.io/application/oauthProcessCode/atlassian-jira
Step 14: Now navigate to “Settings”, again on the left side
Step 15: Scroll to the bottom of the page and capture the Client ID and Secret, these will be required to put in the Clarity Security app integration
Step 16: Go to https://admin.atlassian.com/ and log in. Select the correct organization for your account to log in to that instance of Atlassian
Step 17: Once you have completely logged into your instance, click on settings > API Keys
Step 18: Click "Create API Key" > Name you key something descriptive, and change the expiration date to 1 year from the current date > Click "Create"
Step 19: Copy the Organization ID and API Key that appears
Step 20: Select Settings and make note of the Organization name
Step 21: Select Security > Identity Providers
Step 22: Select Set up user provisioning under Other Providers
Step 23: Copy the values for SCIM base URL and API key
Step 24: Save your SCIM configuration
Step 25: Log in to Clarity Security
Step 26: Select Applications and click Marketplace
Step 27: Search for Atlassian Cloud and click Connect
Step 28: Fill out the Connect App form
Details for fields common to all applications can be found in the following article: Common App Configuration Steps
- admin_organization_id: From Step 19
- admin_api_key: From Step 19
- org_domain: From Step 20
- client_id: From Step 15
- client_secret: From Step 15
- scim_directory_id: From Step 23
- scim_api_key: From Step 23
Step 29: Fill out the App Settings form
Details for fields common to all applications can be found in the following article: Common App Configuration Steps
Step 30: Fill out the User Settings form
The table at the top of this article lists the supported features of this connector.
Details for fields common to all applications can be found in the following article: Common App Configuration Steps
Step 31: Validate Your Selections and Save
Clicking the Save button will trigger the first full sync for your application (even if you selected Manual syncing). This includes Service Users, Entitlements, Service User Entitlements, Service User Attributes.
Need help?
If you have any problems, contact your customer success team. You can also get in touch with our general support via email, open a support ticket. Our general support team is available Monday - Friday from 8:00 AM - 6:30 PM CST.