Integrate Atlassian

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.

Prerequisites

Before you can apply SAML single sign-on to your Atlassian user accounts, you must do the following:

2. 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.

4. Ensure that you have an Atlassian Site set up (for example, an Atlassian site for Confluence). See Set up your site and spaces.

To integrate Atlassian with Identity as a Service, you must do the following:

Step 1: Copy the SAML Configuration from Identity as a Service

Copy the SAML Configuration from Identity as a Service

1. Log into your Identity as a Service administrator account.

2. Click > Security > Applications. The Applications Lists page appears.

3. 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.

4. 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.

Step 2: Export the signing certificate from Identity as a Service

Export a SAML signing certificate

1. Log in to your Identity as a Service administrator account.

1. Click > Security > Applications. The Applications List page appears.

2. Under SAML Cloud Integrations, click SAML Signing Certificates. The SAML Signing Certificates page appears.

3. 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.

a. 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.

b. Click Export.

Step 3: Add Identity as a Service as an Identity Provider in Atlassian

1. Ensure that you have completed the required prerequisites.

2. Log in to Atlassian as an administrator. The Atlassian Home page appears.

3. Click and select Cloud Administration from the Settings menu. The Managed Accounts page appears.

4. Click Security. The Organization insights page appears.

5. In the menu pane, click SAML single sign-on. The SAML Single sign-on page appears.

6. Click Add SAML configuration. The Add SAML configuration dialog box appears.

7. 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.

8. 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.

9. Open the certificate file you exported in Step 2: Export the certificate file from Identity as a Service.

10. Copy the contents of the certificate file and paste it in the Public x509 certificate text box.

11. Click Save Configuration to return to the SAML single sign-on page.

12. 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

13. Enforce single sign-on as follows:

a. In the menu pane, click Authentication policies. The Authentication policies page appears.

b. Click Edit. The default page appears.

c. Click the Settings tab.

d. Under Single sign-on, select Enforce single sign-on.

e. Click Update.

f. Click Enforce on the confirmation prompt to accept the change and return to the Default page.

g. 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.

Step 4: Add Atlassian to Identity as a Service

Add Atlassian as an application to Identity as a Service

1. Log into your Identity as a Service administrator account.

2. Click > Security > Applications. The Applications Lists page appears.

3. Click Add. The Select an Application Template page appears.

4. Under SAML Cloud Integrations, click Atlassian. The Add Atlassian page appears.

5. Enter an Application Name.

6. Enter an Application Description.

7. Optional. Add a custom application logo.

a. Click next to Application Logo. The Upload Logo dialog box appears.

b. Click to select an image file to upload.

c. Browse to select your file and click Open. The Upload Logo dialog box reappears showing your selected image.

d. If required, resize your image.

e. Click OK.

8. Select the Authentication Flow that appears to users during login.

9. Click Next. The General page appears.

10. 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.

11. In the Service Provider Entity ID field, enter the SP Entity ID you copied in Step 3: Add Identity as a Service to Atlassian.

12. 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.

13. Enter the SAML Session Timeout to the time when the SAML Assertion times out. The maximum is 720 minutes.

14. 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.

15. From the SAML NameID Attribute drop-down list, select Email.

16. From the SAML NameID Encoding Format drop-down list, select Email.

17. From the SAML Signing Certificate drop-down list, select the signing certificate.

18. From the SAML Signature Algorithm drop-down list select SHA512.

19. Select Sign Complete URL Response.

20. 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.

21. 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.

22. 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.

23. Deselect Encrypt SAML Assertion.

24. Optional. Add Alternative Assertion Consumer Service URLs, as follows:

a. Click Add.

b. Enter a Name.

c. Enter a URL Value.

d. Select Show in My Profile to display the Alternative Consumer Service URL in a user's My profile page.

e. Optional. Add an Application Logo.

f. Click Add.

g. Repeat these steps to add more Alternative Assertion Consumer Service URLs.

25. Add your Atlassian site as a Relay State, as follows:

a. Under Relay State click Add. The Add Relay State dialog box appears.

b. 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.

c. Optional. Add a Relay State custom logo.

d. Click Add.

26. Include the following user attributes in the SAML assertion, as follows:

Add a first name SAML attribute:

a. Under SAML Attributes, click Add. The SAML Attributes dialog box appears.

b. In the Name field enter:

http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname

c. From the drop-down list, select the Name Format for the attribute.

d. Click Add next to Value(s).

e. In the Values field type < and select <First Name>.

Add a last name SAML attribute:

a. Under SAML Attributes, click Add. The SAML Attributes dialog box appears.

b. In the Name field enter:

http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname

c. From the drop-down list, select the Name Format for the attribute.

d. Click Add next to Value(s).

e. In the Values field type < and select <Last Name>.

Add a unique user ID SAML attribute:

a. Under SAML Attributes, click Add. The SAML Attributes dialog box appears.

b. In the Name field enter:

http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn

c. From the drop-down list, select the Name Format for the attribute.

d. Click Add next to Value(s).

e. In the Values field type < and select <Unique User ID>.

27. Click Submit.

Step 5: Create a resource rule to protect access to Atlassian

Create a resource rule to protect access to a SAML application

1. Log in to your Identity as a Service administrator account.

2. Click > Security > Resource Rules. The Resource Rules List page appears.

3. Click + next to the application you want to protect with a resource rule. The Add Resource Rules page appears.

4. Enter a Rule Name and Rule Description for the resource rule.

5. In the Groups list, select the group or groups of users restricted by the resource rule.

These are the groups to which the resource rule applies. If you do not select any groups, by default the resource rule applies to all groups.

6. Click Next. The Authentication Conditions Settings page appears.

7. Optional: Select Disable Single Sign-On for Application to force a user to re-authenticate whenever they attempt a new login.

8. If you do not Enable Advanced Risk Factors, do the following:

a. Select the Authentication Flow from the drop-down list. The Authentication Flow flowchart updates based on the selection.

b. Click Submit to save the Resource Rule.

9. If you want to Enable Advanced Risk Factors, complete the remaining steps in this procedure.

10. Select Enable Advanced Risk Factors to add additional risk factors to the resource rule.

11. Select Enable Strict Access for Application to set the resource rule to deny access regardless of the outcome from other resource rules. If this option is disabled for any resource rule that denies access, the user is allowed access if at least one resource rule allows access.

12. For each Advanced Risk Factor, click the Deny option to deny access to the application if the risk factor fails regardless of the results of the other risk factors.

13. Click Date/Time to set the conditions as follows:

a. Select one of the following:

– Allow Date/Time to set when a user can access the application.

– Deny Date/Time to set when the user cannot access the application.

The Date/Time Context Condition Settings appear.

b. Select the Condition Type:

– Specific Date Range Condition—Allows or denies access to the application during a select period of days.

– Time-of-day and/or Day of Week Recurring Conditions—Allows or denies access to the application on a specific time of day, day of the week, or both. Recurring times selected only apply to days not denied.

– Clear Selection—Clears existing Date and Time conditions.

c. Set the Condition Type settings, as follows:

i) Select Use local time zone to use the local time zone or deselect Use local time zone to use the local time zone and begin typing the time zone in the Begin Typing Timezone name field and select the time zone from the drop-down list.

ii) If you selected Specific Date Range Condition, click Start Date to select a start date from the pop-up calendar. Optionally, select the End Date.

iii) If you selected Time-of-Day and/or Day-of-Week, click Start Time and select the start time from the pop-up clock. Optionally set the End Time. You must also select the days of the week for the condition.

d. Click Save to return to the Authentication Conditions Settings page.

14. Click Geolocation to set the Location Condition Settings, as follows:

a. Select Allow or Deny to create an allowed or denied country list.

b. From the Selected Countries drop-down list, select the countries to add or deny access to the application. Repeat until you have added all the desired countries to the list.

c. Select Allow Anonymous IP Address to increase the risk of users authenticating from an anonymous IP.

d. Click Save to save to return to the Authentication Conditions Settings page.

15. Click Source IP Address. The IP Address Risk Setting dialog box appears. Do one of the following:

a. Select Custom and add the required IP Allowed Addresses and IP Denied Addresses.

b. Select IP List Address and select the IP List to allow or deny.

c. Select None to not restrict any IP addresses.

d. Click OK to return to the Authentication Conditions Settings.

16. Click Machine Authentication to set the Machine Authentication Condition Settings, as follows:

a. Set the Machine Authentication Risk is less than or equal to the value that the machine authenticator's total risk score must be less than during authentication to pass this condition.

The risk score is based on the attribute differences between a user's Machine Authentication information and that recorded on Identity as a Service before the condition fails. If an attribute does not match, the attribute incurs the number of risk points shown in Non-Matching Risk Points for that attribute. The Non-Matching Risk Points values of each non-matching attribute are added together, resulting in a total risk score. This score is normalized to be out of 100 as follows:

Total Risk Score = (Total Risk Points of Failing Attributes / Maximum Risk Points of All Enabled Attributes) * 100

The resource rule condition fails when the number of non-matching risk points exceeds the Machine Authentication Risk value defined in this step. A value of 0 means that a single attribute difference causes the Device Fingerprint condition to fail. The default value is 3. The value between 0-50 can be entered.

The default value is defined by the Machine Risk Limit. See Modify machine authenticator settings.

b. Click Save.

17. Define the Location History / Known Locations and Travel Velocity conditions. The Risk-Based Authentication (RBA) settings of your Identity as a Service account define the location history and travel velocity conditions. See Manage risk-based authentication settings for more information.

18. Set the Device Certificates risk factor to require the client to perform client-authenticated SSL with a certificate issued from a trusted CA to pass.

19. Set the risk score for application conditions to set the risk percentage a user receives if they fail to meet the condition, as follows:

● Click the dot next to the condition setting and slide the risk scale to the risk percentage

-or-

● Click the 0% and enter the risk points and then click OK.

The default setting is 0%. The Risk percentage determines the authentication requirements as set by the Authentication Decision. When a user attempts to authenticate to an application, the final risk percentage is the sum of all failed conditions.

20. Set the Authentication Decision risk level for Medium Risk and High Risk as follows:

a. Click the risk threshold percentage to the right of Medium Risk or High Risk. The Risk Threshold dialog box appears.

b. Enter the risk percentage.

c. Click OK.

21. Select the Authentication Flows for Low Risk, Medium Risk, and High Risk from the drop-down lists. The Authentication Flows flowchart updates based on your selections.

22. Click Submit to create the resource rule.