Skip to main content

Atlassian

Overview​

Atlassian is a cloud-based service offering that facilitates collaborative work and project management for teams by providing a suite of tools, which include:

  • Jira for project tracking
  • Confluence for document collaboration
  • Bitbucket for version control; and
  • other integrated applications

Below you can find the Aembit configuration required to work with the Atlassian Cloud service as a Server Workload using the Atlassian REST APIs.

Prerequisites​

Before proceeding with the configuration, you will need to have an Atlassian tenant.

Server Workload Configuration​

  1. Create a new Server Workload.
  • Name - Choose a user-friendly name.
  1. Configure the service endpoint:
  • Host - your-domain-name.atlassian.net
  • Application Protocol - HTTP
  • Port - 443 with TLS
  • Forward to Port - 443 with TLS
  • Authentication method - HTTP Authentication
  • Authentication scheme - Basic

Credential Provider Configuration​

  1. Sign into your Atlassian account.

  2. Navigate to the Atlassian account - API Tokens page.

  3. Click on Create API token.

  4. In the dialog that appears, enter a memorable and concise label for your token, and then click Create.

Create Atlassian API token

  1. Click Copy to clipboard and securely store the token for later use in the configuration on the tenant. For more information on how to store your API token, please refer to the official Atlassian documentation.

  2. Create a new Credential Provider.

  • Name - Choose a user-friendly name.
  • Credential Type - Username & Password
  • Username - Your email address for the Atlassian account used to create the token.
  • Password - Provide the token copied from Atlassian.

Client Workload Configuration​

Aembit now handles the credentials required to access the Server Workload, eliminating the need for you to manage them directly. You can safely remove any previously used credentials from the Client Workload.

If you access the Server Workload through an SDK or library, it is possible that the SDK/library may still require credentials to be present for initialization purposes. In this scenario, you can provide placeholder credentials. Aembit will overwrite these placeholder credentials with the appropriate ones during the access process.

Access Policy​

  • Create an Access Policy for a Client Workload to access the Atlassian Server Workload. Assign the newly created Credential Provider to this Access Policy.

Required Features​

  • You will need to configure the TLS Decrypt feature to work with the Atlassian Server Workload.