Integrate with Atlassian Cloud

Use JumpCloud SAML Single Sign On (SSO) to give your users convenient but secure access to all their web applications with a single set of credentials. Integrate your JumpCloud account with Atlassian Cloud through an Identity Management Connector. After you connect JumpCloud with Atlassian Cloud, you can provision, update, and deprovision users and groups. Leverage this integration for centralized user lifecycle management and get immediate attribute management of users bound to integrated applications.

Read this article to learn how to configure the Atlassian Cloud connector. 

Note: As of March 15, 2021, Atlassian administrators will need to configure an authentication policy or policies as appropriate to their environment to enforce logins through SAML. See Atlassian's SSO article for more information.


  • A JumpCloud administrator account.
  • Your domain must be verified with Atlassian. Refer to Atlassian support and documentation for instructions and other restrictions using SAML.
  • SAML workflow requires that the email address be the same between Atlassian and JumpCloud.
  • Atlassian requires Atlassian Access to be enabled to configure SAML. 
  • If there are issues after enabling SAML, go to to log in with Atlassian account credentials and correct any problems.
  • You need an Atlassian Access subscription to create a SCIM integration for Identity Management.
  • You need to create a Directory token in Atlassian Cloud for JumpCloud, before configuring a JumpCloud Identity Management connector. Learn more about creating SCIM tokens
  • If you need to renew your token, you must deactivate the Identity Management integration , renew your token and then reactivate the integration.
  • Save the Directory Base URL and API Key to use when you configure a JumpCloud Identity Management Connector. 
  • We recommend that you configure SSO for Atlassian Cloud prior to creating an Identity Management integration with Atlassian Cloud for the following reasons:
    • An inactive Atlassian Cloud application will be shown in the User Portal unless you deselect this option in the application panel.
    • Atlassian Cloud currently requires a verified domain for your organization. Learn more about verifying a domain and managing accounts.

Important Considerations

  • Users can be provisioned to any Atlassian Cloud products that are administered through your Atlassian Access subscription.
  • SAML is the recommended method for managing secure user authentication into Atlassian Cloud.
  • If you delete an integrated Atlassian Cloud application from your Applications list, the application is removed from JumpCloud. Any previously associated users remain active in Atlassian Cloud. These users are able to log in to Atlassian Cloud with the password they used prior to your enablement of SSO to the Atlassian Cloud application from your JumpCloud account.
  • If you deactivate Identity Management on your Atlassian Cloud application in JumpCloud, previously connected users remain active in Atlassian Cloud and are able to authenticate using SSO. After deactivation, updates will no longer be made to user accounts through the Identity Management integration.
  • A user’s email address must belong to an Atlassian Cloud verified domain for them to be created and updated.
  • Update product access settings on the Atlassian Directory integration group to automate product access for users created by JumpCloud as the Identity Provider.
  • Don’t add the same user group to multiple Atlassian Cloud connectors in JumpCloud. If you do, users who are members of that user group will be deactivated in the application if one of the connectors is removed from the user group.
  • You can only sync up to 5,000 users, because some Atlassian products have an upper limit for total supported users. Atlassian stops syncing new users after 5,000.

Group Management Considerations

Enabling Group Management

You must select the Enable management of User Groups and Group Membership in this application option to manage groups and group membership in the application from JumpCloud.

Group Provisioning and Syncing 
  • Empty groups are not created.
  • JumpCloud takes over management of existing groups in the application when the user group name in JumpCloud matches the name of the group in the application.
  • All user groups associated with the application in JumpCloud are synced. Syncing occurs whenever there is a membership or group change event.
  • Group renaming is supported.
  • If a user group is disassociated from the application in JumpCloud, syncing immediately stops and the group is left as-is in the application. All members of that user group are deactivated in the application unless they are associated with another active application group that is managed from JumpCloud.
Group Deletion
  • Managed groups deleted in JumpCloud are deleted in the application.
  • All members of the deleted group are deactivated in the application, unless they are associated with another active application group that is managed from JumpCloud.
Disabling Group Management
  • You can disable group and group membership management by unchecking the Enable management of User Groups and Group Membership in this application option.
  • The managed groups and group membership are left as-is in the application.
  • JumpCloud stops sending group membership information for the user, but the user’s identity will continue to be managed from JumpCloud.

Creating a new JumpCloud Application Integration

  1. Log in to the JumpCloud Admin Portal.
  2. Navigate to USER AUTHENTICATION SSO Applications.
  3. Click + Add New Application.
  4. Type the name of the application in the Search field and select it.
  5. Click Next.
  6. In the Display Label, type your name for the application. Optionally, you can enter a Description, adjust the User Portal Image and choose to hide or Show in User Portal.
  7. Click Save Application.
  8. If successful, click:
    • Configure Application and go to the next section.
    • Close to configure your new connector at a later time.

Configuring the SSO Integration

To configure JumpCloud 1

  1. Create a new application or select it from the Configured Applications list.
  2. Select the SSO tab.
  3. Replace any instances of YOUR_ORG_NAME with your Atlassian Cloud organization name.
  4. Select save.

To download the certificate

  1. Find your application in the Configured Applications list and click anywhere in the row to reopen its configuration window.
  2. Select the SSO tab and click IDP Certificate Valid > Download certificate.


The certificate.pem will download to your local Downloads folder.

To configure Atlassian Cloud

  1. Login to the Atlassian admin console. 
  2. Go to Security > SAML single sign-on.
  3. Click Add SAML configuration
  4. In the Identity provider Entity ID field, enter the IdP Entity ID from JumpCloud.
  5. In the Identity provider SSO URL field, enter the IDP URL from JumpCloud.
  6. In the Public x509 certificate field, enter the contents of the certificate you prepared in previous section.
  7. In the “Information required by your Identity Provider” section, you will see information displayed for:
    • SP Identity ID
    • SP Assertion Consumer Service URL (ACS URL)
  8. Copy the SP Identity ID and the SP ACS URL  values for use during configuration of the JumpCloud SSO Application Part 2.
  9. Keep the Atlassian administrator console open.

To configure JumpCloud 2

  1. Open the Atlassian connector in JumpCloud. 
  2. For SP Entity ID, copy and enter the SP Identity ID from Atlassian.
  3. For ACS URL, copy and enter the ACS URL from Atlassian. 
  4. Click save

Granting User Access to SSO in Atlassian Cloud

By default, users are created in the local directory in Atlassian Cloud. To grant them access to SSO, you need to move the users to the directory created for SSO with the verified domain.

  1. In your Atlassian Cloud portal, navigate to USER SECURITY > Authentication Policies.
  2. Click Edit in the Users in local directory pane.
  3. For the users you wish to grant SSO access to, click Change Policy.
  4. Select the name of the policy that you created for SSO in the drop-down menu.
  5. Click Change.
  6. Return to USER SECURITY > Authentication Policies.
  7. Click Edit in your policy created for SSO.
  8. Click Members and select Enforce single sign-on.

Authorizing User SSO Access

Users are implicitly denied access to applications. After you connect an application to JumpCloud, you need to authorize user access to that application. You can authorize user access from the Application Configuration panel or from the Groups Configuration panel. 

To authorize user access from the Application Configuration panel

  1. Log in to the JumpCloud Admin Portal.
  2. Go to USER AUTHENTICATION > SSO Applications, then select the application to which you want to authorize user access.
  3. Select the User Groups tab. If you need to create a new group of users, see Get Started: Groups.
  4. Select the check box next to the group of users you want to give access.
  5. Click save

To learn how to authorize user access from the Groups Configuration panel, see Authorize Users to an SSO Application.

Validating SSO authentication workflow(s)

IdP Initiated

  • Access the JumpCloud User Console.
  • Select the application’s tile.
  • The application will launch and login the user.

SP Initiated

  • Navigate to your Service Provider application URL.
  • You will be redirected to log in to the JumpCloud User Portal.
  • The browser will be redirected back to the application and be automatically logged in.

Using JIT Provisioning

The attributes required for JIT provisioning are already included for SAML/SSO authentication. 

To complete the provisioning process:

  1. Authorize a user’s access to the application in the identity provider. See Authorize User Access.
  2. Have the user log in to the application using SSO. The SAML assertion passes from JumpCloud to the service provider, and gives the service provider the information it needs to create the user account.

Configuring the Identity Management Integration

To configure Atlassian Cloud

  1. Go to Select your organization if you have more than one.
  2. Select Security > Identity providers.
  3. Select your Identity provider Directory.
  4. Select Set up user provisioning.
  5. Copy the values for SCIM base URL and API key.
  6. Save your SCIM configuration.


The secret (token) may only be shown once. Copy it to a secure location, like the JumpCloud Password Manager, for future reference.

Make sure you have a site in your organization

Users are synced to sites and products in your organization. When you provision users to an organization, you need to grant them access to products. You can do this after you add a site for a product.

  1. Go to Select your organization if you have more than one.
  2. Select Products.
  3. Select Add product.
  4. Select a product you’d like to add.
  5. Enter the Site name (for example,

Configure product access for the provisioned groups and users

To grant product access to provisioned users, you need to set up product access for existing groups.

  1. From the site ( you added, go to Product access and find the product you’d like to add the group to.
  2. Select Add group and select or enter the name of the synchronized group.
  3. Select Add groups to finish giving the group product access.

You'll see a success flag that confirms the group is configured for product access. Learn more about configuring product access

To configure JumpCloud

  1. Create a new application or select it from the Configured Applications list.
  2. Select the Identity Management tab.


The IdP URL can't be shared across applications and can't be edited after it's created.

  1. Click Enable management of User Groups and Group Membership in this application if you want to provision, manage, and sync groups.
  2. Click Configure.
  3. You’re presented with two fields:
    • *SP Base URL: Paste the Directory Base URL you saved when you created the Directory for JumpCloud in Atlassian Cloud.
    • *SP API Token: Paste your Atlassian Cloud API Key.
  4. Click save.
  5. You will receive a confirmation that the Identity Management integration has been successfully verified.

Attribute Mappings

The following table lists attributes that JumpCloud sends to the application. See Attribute Considerations for more information regarding attribute mapping considerations. 

Learn about JumpCloud Properties and how they work with system users in our API

JumpCloud Property JumpCloud UI Attribute Name Value and Validation in JumpCloud Atlassian Cloud Attribute
email Company Email string emails: value
username Username string username
firstname First Name string name.givenName
lastname Last Name string name.familyName
suspended suspended boolean active:false = inactive
created Created Date string default
_id Object ID string SCIM user id
middlename Middle Name string name.middleName
displayname Display Name string name.displayName
company Company string organization
jobTitle Job Title string title
department Department string department
addresses: locality   string address
phoneNumbers: type [=work phone “business”] Work Phone string phone
phoneNumbers:number Work Phone string phone

Importing Users

This functionality is helpful if users have already been created in the application but have not been created in JumpCloud.

  1. Log in to the JumpCloud Admin Portal.
  2. Go to USER AUTHENTICATION > SSO Applications.
  3. Search for the application and click to open its configuration panel. 
  4. Select the Identity Management tab.
  5. Click manual import.
  6. Select the users you want to create in JumpCloud from the application from the list of users that appear. Users in the list have two import statuses:
  • New – The user has not been imported.
  • Imported – user has been imported and has an account in JumpCloud.

Tip: Try using the New Users-only filter when selecting users to import. This will move all of your new users to the top of the list, making them easier to identify and select.

  1. Click import.
  • If you are importing less than 100 users, your import results will display in real time and you can continue onboarding your users. 
  • If you have more than 100 users being imported, JumpCloud will send you an email when your import is complete.
  1. You can now connect and grant users access to all their JumpCloud resources. Learn more in the Authorize Users to an Application and Connecting Users to Resources articles.

Warning: Imported users must be members of a user group bound to an application for JumpCloud to manage their identity in, and access to, the application.

Removing the Integration

To deactivate the IdM Integration

  1. Log in to the JumpCloud Admin Portal.
  2. Go to USER AUTHENTICATION > SSO Applications.
  3. Search for the application that you’d like to deactivate and click to open its details panel. 
  4. Under the company name and logo on the left hand panel, click the Deactivate IdM connection link.
  5. Click confirm
  6. If successful, you will receive a confirmation message.

To deactivate the SSO Integration

  1. Log in to the JumpCloud Admin Portal.
  2. Go to USER AUTHENTICATION > SSO Applications.
  3. Search for the application that you’d like to deactivate and click to open its details panel. 
  4. Select the SSO tab.
  5. Scroll to the bottom of the configuration.
  6. Click Deactivate SSO
  7. Click save
  8. If successful, you will receive a confirmation message.

To delete the application

  1. Log in to the JumpCloud Admin Portal.
  2. Go to USER AUTHENTICATION > SSO Applications.
  3. Search for the application that you’d like to delete and click to open its details panel.
  4. Check the box for the application.
  5. Click Delete.
  6. Enter the number of the applications you are deleting
  7. Click Delete Application.
  8. If successful, you will see an application deletion confirmation notification.

List IconIn this Article

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case