Atlassian Access offers enhanced security and centralized administration that works across Atlassian cloud products (see https://atlassian.com). You can protect access to Atlassian by integrating Atlassian with Identity as a Service. Once integrated, users can use single sign-on to log in to their Atlassian account through Identity as a Service.
Note: This integration was tested using Identity as a Service version 5.14 and Atlassian Cloud from Jan 11 to Jan 18, 2021. Other versions of Atlassian Cloud may require integration and configuration steps that differ from those documented in this procedure. For other versions of Atlassian Cloud, this integration guide may be used as an initial approach for integrating Atlassian Cloud. In the event of other issues, contact support@entrust.com for assistance.
Before you can apply SAML single sign-on to your Atlassian user accounts, you must do the following:
Create an organization (see Explore an Atlassian Organization).
Verify one or more domains to confirm you own them. See Verify a domain for your organization. When you verify a domain, all the Atlassian accounts that use email addresses from the verified domain become managed by your organization.
Subscribe to Atlassian Access. See Subscribe to Atlassian Access.
Ensure that you have an Atlassian Site set up (for example, an Atlassian site for Confluence). See Set up your site and spaces.
Copy the SAML Configuration from Identity as a Service
Log into your Identity as a Service administrator account.
Click
> Security > Applications. The Applications Lists page appears.
Under SAML Cloud Integrations, click SAML Configuration. The SAML Configuration dialog box appears.
This dialog box contains information you need to configure your SAML application for Identity as a Service authentication.
Do one of the following:
Leave this dialog box open to reference later in this procedure.
Copy the Entity ID, Single Sign-on URL, and Single Logout URL to a text file and save it to reference later in this procedure.
Note: Depending on the integration you are performing, you may not need all three of these SAML configuration values.
Export a SAML signing certificate
Log in to your Identity as a Service administrator account.
Click
> Security > Applications. The Applications List page appears.
Under SAML Cloud Integrations, click SAML Signing Certificates. The SAML Signing Certificates page appears.
Click
next to the certificate to export the certificate you want to import into your SAML service provider application. The Export Certificate dialog box appears.
If the certificate has been issued by a CA, do one of the following:
Click Certificate to export the self-signed certificate.
Click Root CA Certificate to export a certificate issued from a CA.
Click Certificate Chain to export the SAML signing certificate and its CA certificates.
Click Export.
Ensure that you have completed the required prerequisites.
Log in to Atlassian as an administrator. The Atlassian Home page appears.
Click
and select Cloud Administration from the Settings menu. The Managed Accounts page appears.
Click Security. The Organization insights page appears.
In the menu pane, click SAML single sign-on. The SAML Single sign-on page appears.
Click Add SAML configuration. The Add SAML configuration dialog box appears.
In the Identity provider Entity ID field, enter the Entity ID you copied in Step 1: Copy the SAML configurations from Identity as a Service.
In the Identity provider SSO URL field, paste the Single-Sign-On URL you copied in Step 1: Copy the SAML configurations from Identity as a Service.
Open the certificate file you exported in Step 2: Export the certificate file from Identity as a Service.
Copy the contents of the certificate file and paste it in the Public x509 certificate text box.
Click Save Configuration to return to the SAML single sign-on page.
On the Single sign-on page, copy and save the following from the Information required by your identity provider into a text editor, such as Notepad. You need this information for Step 4: Add Atlassian to Identity as a Service.
SP Entity ID
SP Assertion Consumer Service URL
Enforce single sign-on as follows:
In the menu pane, click Authentication policies. The Authentication policies page appears.
Click Edit. The default page appears.
Click the Settings tab.
Under Single sign-on, select Enforce single sign-on.
Click Update.
Click Enforce on the confirmation prompt to accept the change and return to the Default page.
Click the Members tab. This page shows the list of Users forced to use single-sign on for your site.
Note: Before you begin this step, ensure that you have completed the required Atlassian set up. See Prerequisites.
Add Atlassian as an application to Identity as a Service
Log into your Identity as a Service administrator account.
Click
> Security > Applications. The Applications Lists page appears.
Click Add. The Select an Application Template page appears.
Do one of the following:
Select SAML Cloud Integrations from the search drop-down list and scroll to find the application you want to add to IDaaS.
- or -
In the Search bar, enter a search option to filter for the application you want to add to IDaaS.
Click Atlassian. The Add Atlassian page appears.
Enter an Application Name.
Enter an Application Description.
Optional. Add a custom application logo.
Click
next to Application Logo. The Upload Logo dialog box appears.
Click
to select an image file to upload.
Browse to select your file and click Open. The Upload Logo dialog box reappears showing your selected image.
If required, resize your image.
Click OK.
Select the Authentication Flow that appears to users during login.
Click Next. The General page appears.
In the Default Assertion Consumer Service URL field, enter the SP Assertion Consumer Service URL you copied in Step 3: Add Identity as a Service to Atlassian.
In the Service Provider Entity ID field, enter the SP Entity ID you copied in Step 3: Add Identity as a Service to Atlassian.
Optional. Enter the SAML Username Parameter Name used to identity the user ID being requested for authentication. The user ID can then be passed as a parameter, for example, Username=jdoe.
Enter the SAML Session Timeout to the time when the SAML Assertion times out. The maximum is 720 minutes.
Enter the Max Authentication Age (seconds) to set the maximum amount of time that can elapse before a user is required to reauthenticate during a new login attempt. This applies for both SP-initiated and IDP-initiated login. Set this field to -1 to disable this feature.
From the SAML NameID Attribute drop-down list, select Email.
From the SAML NameID Encoding Format drop-down list, select Email.
From the SAML Signing Certificate drop-down list, select the signing certificate.
From the SAML Signature Algorithm drop-down list select SHA512.
Select Sign Complete URL Response.
Optional: Select Respond Immediately for Unsuccessful Responses to return to the application immediately after a login failure, rather than allow user to try again with a different userID.
Deselect Enable Go Back Button if you do not want users to be able to go back to the Atlassian login page to log in.
Select Show Default Assertion Consumer URL Service in the My Profile. When selected, the Default Assertion Consumer URL appears in a user's My Profile page in addition to relay states and Alternative Assertion Consumer URLs.
Deselect Encrypt SAML Assertion.
Optional. Add Alternative Assertion Consumer Service URLs, as follows:
Click Add.
Enter a Name.
Enter a URL Value.
Select Show in My Profile to display the Alternative Consumer Service URL in a user's My profile page.
Optional. Add an Application Logo.
Click Add.
Repeat these steps to add more Alternative Assertion Consumer Service URLs.
Add your Atlassian site as a Relay State, as follows:
Under Relay State click Add. The Add Relay State dialog box appears.
Enter a Name for the relay state.
Example: https://yoursite.atlassian.net
Notes: Relay states appear on the user's My Profile page. If you do not want it to appear on the user's profile page, click
next to the relay state to disable it. If at any time you want to re-enable it, click
.
Relay states apply to the Default Assertion Consumer Service URLs and not the Alternative Assertion Consumers URLs.
Optional. Add a Relay State custom logo.
Click Add.
Repeat these steps to add more Relay States.
Include the following user attributes in the SAML assertion, as follows:
Add a first name SAML attribute:
Under SAML Attributes, click Add. The SAML Attributes dialog box appears.
In the Name field enter:
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname
Click Add next to Value(s).
In the Values field type < and select <First Name>.
Add a last name SAML attribute:
Under SAML Attributes, click Add. The SAML Attributes dialog box appears.
In the Name field enter:
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname
Click Add next to Value(s).
In the Values field type < and select <Last Name>.
Add a unique user ID SAML attribute:
Under SAML Attributes, click Add. The SAML Attributes dialog box appears.
In the Name field enter:
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn
Click Add next to Value(s).
In the Values field type < and select <Unique User ID>.
Click Submit.
Step 5: Add a resource ruleStep 5: Add a resource rule
Step 6: Test the integrationStep 6: Test the integration
Testing Service Provider Login
Open a Web browser and enter the URL for your Atlassian account. You are directed to Identity as a Service.
Enter your Atlassian account User ID and click Next.
Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to the Atlassian Home page.
Testing Identity as a Service redirect log in
Log in to your Identity as a Service account.
Go to your My Profile page if you are not already there.
Under Applications, click Atlassian.
Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to Atlassian.