Connecting SailPoint and Atlassian Suite SaaS

To connect SailPoint with Atlassian Suite, perform the following tasks:

Adding the Source in SailPoint

To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs.

To configure a new source:

1. Sign in to SailPoint.
2. Go to Admin > Connections > Sources.
3. Select Create New.
4. Search for the connector by entering the name in the search box, and then select Actions.

5. In the Actions dropdown list, select the setup method:

   • Express Setup - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started.

     Note

     Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to Credential Providers. For more information, contact your SailPoint Customer Service Manager.

   • Standard Setup - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

Configuring a Source Using Express Setup

Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data.

1. Review the directions and select Start Express Setup.

2. Review the pre-populated Source Name, Source Owner, and Description. To update, select Edit.

   Note

   The source name must be unique. You can change these settings later in the source configuration.

3. (Optional) If enabled for your organization, select the Use a Credential Provider checkbox to manage the source's authentication using a credential provider.

   Note

   To add a Credential Provider in SailPoint, go to Admin > Connections > Credential Providers. For more information about credential providers, refer to Credential Providers.

4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the Connection Settings section.

5. Select Finish.

   After a successful test connection, the system creates your source and prompts you to run an aggregation.

   • If you want to aggregate now, select Aggregate.

     • To see the latest account aggregation history, go to Account Management > Account Aggregation.
     • To see the list of aggregated source accounts, go to Account Management > Accounts.

   • If you want to aggregate later, select Exit. This returns you to the Sources page. Your new source is listed, but contains no accounts or aggregation history yet.

Configuring a Source Using Standard Setup

Use Standard Setup to configure the connector for full feature support.

1. In the Source Name field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
2. In the Description field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters.
3. In the Source Owner field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to Assigning a Source Owner.
4. (Optional) Select a governance group to grant its members source or role sub-admin level oversight of the source and its access. For more information, refer to Creating and Managing Governance Groups.
5. If this source represents a primary system containing your organization's personnel records, select the Authoritative Source checkbox. For more information, refer to Creating Identity Profiles.
6. Select Continue. The source is created, and you are navigated to the Source Setup > Base Configuration page. Continue to configure your connected source there.

Base Configuration

Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary.

1. Enter a unique name and description for the source.

2. In the Source Owner dropdown list, select the identity that owns this source.

   • To find a source owner, begin entering their name.

3. (Optional) If enabled for your organization, select the Use a Credential Provider checkbox to manage the source's authentication using a credential provider.

   Note

   To add a credential provider, go to Admin > Connections > Credential Providers. For more information about credential providers, refer to Credential Providers.

4. Configure the authentication to allow SailPoint to connect to the source. Refer to Connection Settings for more information.

5. (Optional) In the Governance Group for Source Management dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to Associating Governance Groups with a Source.

6. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default.

   • Enable Provisioning - Set the toggle to Enabled to allow the source to create, update, and deactivate accounts in the connected source system.

   • Disable Provisioning - Set the toggle to Disabled to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source.

7. Select Save.

Connection Settings

Provide the information required for SailPoint to connect and authenticate with Atlassian Suite Cloud.

1. Enter the Site URL (HTTPS API URL) for the cloud instance. For example:

   https://contoso.atlassian.net

2. Enter the Email Address of the Atlassian Jira instance administrator account that you want to configure to execute transactions.

3. Choose the appropriate Authentication Type and provide the information required to connect and interact with the source. The following Authentication Types are supported:

   • Basic
   • Service Account

Basic Authentication

1. Enter the Email Address of the Atlassian Jira instance administrator account that you want to configure to execute transactions.

2. Enter the Site Admin API Token for the instance administrator. The Site Admin API Token is generated in the source.

   For more information, refer to Manage API tokens for your Atlassian account in the Atlassian documentation.

   Note

   The linked document is not maintained by SailPoint and is subject to change without notice.

   Note

   Atlassian API tokens don’t use selectable scopes like OAuth scopes. They inherit the creator’s Atlassian roles, so use an account with the required admin role when creating the token. Create the API token without scope.

Service Account Authentication

1. Enter the Email Address of the Atlassian Jira service account.
2. Enter the Service Account API Token.

3. Use a scoped API token generated for a service account that has Jira product access and the required permissions. The token must include these classic scopes:

   • read:jira-work
   • read:jira-user
   • manage:jira-configuration
   • manage:jira-project

   For more information, refer to Manage API tokens for service accounts.

4. (Optional) Enter Confluence Scoped API Token for NHI Discovery from Confluence.

Once the Authentication Type is selected perform the following steps:

1. (Optional) Enter the Org Admin API Token for the instance administrator. This is required to enable, disable accounts or discover Non Human Identities. The Org Admin API Token is generated in the source.

   For more information, refer to Manage an organization with the admin APIs in the Atlassian documentation.

   Note

   The linked document is not maintained by SailPoint and is subject to change without notice.

2. (Optional) Enter the Connection Timeout (in minutes) to hold the connection with the Atlassian system in an idle state. The default is 1 minute.

3. Select Save.

Activity Insights Settings

SailPoint pulls in activity data in the form of events like user logins, password changes, and content updates within the application. You can view an identity’s activity data within an application to discover trends for that user.

Activity Insights Settings allows you to gather account information and activity data from Atlassian Suite. To enable Activity Insights for the Atlassian Suite application, refer to Prerequisites for more information.

To configure Activity Insights, complete the following:

1. Go to Activity Insights Settings.
2. Select Enable Activity Insights to view access to data insights on source and application activity such as logins and other app-specific events.
3. Select Save.

Aggregation Settings

Configure the aggregation parameters such as filter conditions and page size. Use a semicolon delimiter to add multiple filter conditions.

For more information about aggregation, refer to Loading Account Data.

1. Go to Additional Settings > Aggregation Settings.

2. (Optional) Select Aggregate Inactive Users to aggregate inactive users along with active users.

3. (Optional) Enter or paste the Account Filter to filter accounts during aggregation. Only strings are supported as a filter condition. For multiple conditions, use a semicolon delimiter. For example:

   • For single conditions, john aggregates only those accounts whose display name or email prefix contain the name john.
   • For multiple conditions, john;chris aggregates all users whose display name or email prefix are john or chris.

4. (Optional) In the Page Size field, enter the number of records to fetch per page. The default is 50 records per page. The minimum value is 1 and the maximum is 1000.

1. Select Save.

Advanced Settings

In this section, you can provide settings for API Version, Thread Count, and Connection Timeout.

1. Go to Additional Settings > Advanced Settings.
2. (Optional) Select the API Version to use for the connection. The default is 2.
3. (Optional) In the Thread Count field, specify the maximum number of threads for account aggregation. The default is 8.
4. (Optional) Enter the Connection Timeout in Minutes to hold the HTTP connection with the Atlassian system in an idle state. The default is 1 minute.
5. Select Save.

Review and Test

Perform a test to confirm the connection to SailPoint.

1. Go to Review and Test.

2. Confirm that the entries in each field are correct.

   If you note any mistakes, return to the section and make corrections.

3. Select Test Connection.

SailPoint Application Onboarding

SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to Discovered Applications in the SailPoint user interface.

For more information, refer to Application Onboarding in the SailPoint SaaS documentation.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.