Skip to content
vScope Support Page

Atlassian

Connect Atlassian to vScope to inventory the managed user accounts in your Atlassian organization. To inventory Jira Cloud itself, see Jira Cloud.

Prerequisites

Section titled “Prerequisites”
  • An Atlassian organization at admin.atlassian.com. You need to be, or have help from, an organization admin.
  • An organization API key (created in Create an organization API key).
  • Your Organization ID, found in the URL when you open your organization in Atlassian Administration, for example 0a1b2c3d-... in https://admin.atlassian.com/o/0a1b2c3d-.../overview.
  • Network access from the vScope server or Discovery Proxy to https://api.atlassian.com over HTTPS (port 443).

Create an organization API key

Section titled “Create an organization API key”
  1. Sign in to admin.atlassian.com as an organization admin.
  2. Select your organization.
  3. Go to Settings > API keys.
  4. Click Create API key.
  5. Name the key, for example vScope, and set an expiration according to your security policy. Renew the key before it expires and update the credential in vScope.
  6. Click Create and copy the API key. It is only shown once.

Add the Atlassian credential in vScope

Section titled “Add the Atlassian credential in vScope”
  1. In vScope, go to Discovery > Credentials.
  2. Click Create credential and choose Atlassian.
  3. In Organization ID, enter your Organization ID.
  4. In API Key, paste the key you copied. Enter only the key. vScope adds the Bearer prefix automatically.
  5. Optional: add a Note to describe the credential.
  6. Optional: assign a Proxy if vScope should connect to Atlassian through a Discovery Proxy.
  7. Click Test Credential.
  8. Save the credential and run discovery.

Confirm the result

Section titled “Confirm the result”

After discovery completes, the Atlassian accounts appear under User Account in vScope.

Troubleshooting

Section titled “Troubleshooting”

Authentication fails

Section titled “Authentication fails”

Atlassian returns 401 when the API key is wrong, expired, or revoked. Confirm that the API Key is current and has not been revoked in Atlassian Administration.

Permission errors

Section titled “Permission errors”

Atlassian returns 403 or 404 when the key cannot read the organization. Check that:

  1. The key was created by an organization admin.
  2. The Organization ID matches the ID in https://admin.atlassian.com/o/<organization-id> exactly.
  3. The key was created for this organization, not another one.

No or partial inventory

Section titled “No or partial inventory”

If the credential test succeeds but the inventory is incomplete:

  1. Confirm the vScope server or Discovery Proxy can reach https://api.atlassian.com on HTTPS (port 443).
  2. Run a new discovery.

Only managed accounts, meaning accounts from a domain your organization has verified, are included. Accounts outside your verified domains are not.

See also

Section titled “See also”