--- sourceDocument: Australia Asset Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-asset-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Asset Management ft:clusterId : - itam bundleId : - itam workflow : - Technology --- # Integrate with Jira Software Cloud using OAuth 2.0 # Integrate with Jira Software Cloud using OAuth 2.0 {#ariaid-title1} * Release version: Australia * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 10 minutes to read Integrate the Software Asset Management application with your Jira account using OAuth to authenticate ServiceNow requests. Important: Minimize security risks and protect information by granting access only to the necessary user or API permissions.{#integrate-with-jira-oauth__table_box__entry__3} | Process | Required user role in the Jira Software Cloud application | Authentication scopes | |-|-|-| | Download subscriptions | Permission to access Jira | Applicable for Australia release, Software Asset Management - SaaS License Management (sn_sam_saas_int) store app version earlier than 17.4.1. * read:application-role:jira * read:group:jira * read:user:jira * read:avatar:jira {#integrate-with-jira-oauth__ul_pbx_m4p_pbc} Applicable for Australia release, Software Asset Management - SaaS License Management (sn_sam_saas_int) store app version 17.4.1 or later. * read:user:jira * read:group:jira * read:avatar:jira {#integrate-with-jira-oauth__ul_btk_5fk_tjc} | | Pull user activity | * Administer Jira global permission * Browse projects permission for the project containing the issue.If issue-level security is configured, issue-level security permission to view the issue. {#integrate-with-jira-oauth__ul_ut4_d3b_ybc} | Applicable for Australia release, Software Asset Management - SaaS License Management (sn_sam_saas_int) store app version earlier than 17.4.1. * read:user:jira * read:issue-details:jira * read:audit-log:jira * read:avatar:jira * read:field-configuration:jira * read:issue-meta:jira {#integrate-with-jira-oauth__ul_ghz_lqp_pbc} Applicable for Australia release, Software Asset Management - SaaS License Management (sn_sam_saas_int) store app version 17.4.1 or later. * read:jira-user * read:audit-log:jira * read:jira-work {#integrate-with-jira-oauth__ul_ikr_qhk_tjc} | | Reclaim subscription | Site administration, that is, member of the site-admin group | Applicable for Australia release, Software Asset Management - SaaS License Management (sn_sam_saas_int) store app version earlier than 17.4.1. * read:group:jira * write:group:jira {#integrate-with-jira-oauth__ul_iwr_j3b_ybc} Applicable for Australia release, Software Asset Management - SaaS License Management (sn_sam_saas_int) store app version 17.4.1 or later. * read:group:jira * manage:jira-configuration {#integrate-with-jira-oauth__ul_u35_p3k_tjc} | [Table 1. Minimal user permissions] {#integrate-with-jira-oauth__box-title} ## Create an OAuth 2.0 integration in Jira account {#ariaid-title2} Create an OAuth 2.0 integration in the Atlassian Developer console to authenticate the requests. ### Before you begin Important: This procedure is applicable for the Australia release, Software Asset Management - SaaS License Management (sn_sam_saas_int) store app version 17.4.0 or earlier. If you're on version 17.4.1 or later, skip this task and proceed directly to [Obtain the Cloud ID value of Jira instance](https://www.servicenow.com/docs/cS0bvrJ9OdWO1IW6ALEM~w#obt-val-cldid "Obtain the value of the Cloud ID of the Jira cloud instance. This value is required during the configuration of the connection record in your ServiceNow instance."). Jira Role required: Refer the [Minimal user permissions](https://www.servicenow.com/docs/cS0bvrJ9OdWO1IW6ALEM~w#integrate-with-jira-oauth "Integrate the Software Asset Management application with your Jira account using OAuth to authenticate ServiceNow requests.") table. ### Procedure 1. Log in to [Atlassian Developer console](https://id.atlassian.com/login?continue=https://developer.atlassian.com/console/myapps/). 2. Under My apps, select Create and select OAuth 2.0 integration. 3. On the form, provide a name for the integration and select Create. The integration is created and the value of App ID is displayed. 4. Select Authorization. 1. Select Add under Action. 2. In Callback URL, provide the URL of your ServiceNow instance in this format: https://\.service-now.com/oauth_redirect.do. For example, https://example.service-now.com/oauth_redirect.do. 3. Select Save changes. {#create-oauth-int-jira__substeps_j1m_cd5_mwb} 5. Select Settings. 6. Under Authentication details, copy the values of Client ID and Client Secret. 7. Select PermissionsJira APIConfigure. 8. Select the Granular scopes tab. 9. Select Edit Scopes to add the following scopes: * read:application-role:jira * read:group:jira * read:user:jira * read:avatar:jira * read:audit-log:jira * read:issue-details:jira * read:field-configuration:jira * read:issue-meta:jira * write:group:jira {#create-oauth-int-jira__ul_jtr_h25_mwb}You can configure other scopes according to your requirement. ## Obtain the Cloud ID value of Jira instance {#ariaid-title3} Obtain the value of the Cloud ID of the Jira cloud instance. This value is required during the configuration of the connection record in your ServiceNow instance. ### Before you begin Jira Role required: admin ### Procedure 1. Log in to [Atlassian Administration](https://admin.atlassian.com/). 2. Select the Select button against the required organization. 3. On the side navigation pane, select AppsAtlassian apps. 4. On the Atlassian Apps page, select Manage product on the Jira product row. The URL is in the following format in a new window: https://admin.atlassian.com/o/\/atlassian-apps/jira-software/\. 5. Copy the value of Cloud ID and secure it for later use. ## Create a Jira Software Cloud integration profile {#ariaid-title4} Create an integration profile to track software subscriptions and optimize licensing for Atlassian Jira Software Cloud. ### Before you begin To create a Jira integration profile, request the Software Asset Management - SaaS License Management plugin (sn_sam_saas_int) from the [ServiceNow Store](https://store.servicenow.com/). To enable the integration profile to retrieve and update user activity through the Jira Update User Activity subflow, set the com.glide.transform.json.max-partial-length system property Value to 32768. Atlassian Role required: site admin ServiceNow Role required: sam_integrator Important: You must select the Jira Spoke check box for this integration while installing optional features on the [Application Manager](https://www.servicenow.com/docs/access?context=application-manager&version=australia&pubname=australia-platform-administration&ft:locale=en-US) page. For more information about choosing the required SaaS applications, see [Request SaaS License Management](https://www.servicenow.com/docs/ltQ10fYPUIpL7abgEH0~7A "Request the Software Asset Management - SaaS License Management plugin (sn_sam_saas_int) so that you can create and manage integrations with your SaaS and Single Sign-on (SSO) applications. You can use these integrations to track license usage and to reclaim unused licenses."). ### About this task If you're using Software Asset Workspace, the option to create the Jira integration profile in Core UI is inactive. ### Procedure 1. Navigate to the integration profile. | Interface | Action | | Core UI | 1. Navigate to AllSoftware AssetSaaS LicenseDirect Integration Profiles. 2. Select New. 3. Select Jira Integration Profile. {#create-integration-jira__ol_ijd_bjk_qtb} | | Software Asset Workspace | 1. Navigate to License operationsUser SubscriptionsDirect integration profiles. 2. Select New. 3. Select Jira from the drop-down list. 4. Select Continue. {#create-integration-jira__ol_wjd_bjk_qtb} | |-|-| {#create-integration-jira__choicetable_o3p_z3k_qtb} 2. On the form, fill in the fields. {#create-integration-jira__table_iqh_2y5_mjb__entry__2} | Field | Value | |-|-| | Display name | Name of your choice. For example, Jira integration. | | Status | Status of the integration profile. * If you have not published the integration profile, this field is automatically set to Draft. * If you have already published the integration profile, this field is automatically set to Published. {#create-integration-jira__ul_wpy_zvq_dcc} | | Profile type | Jira Subscription. This field is automatically populated. | [Table 2. Integration Profile form] {#create-integration-jira__table_iqh_2y5_mjb} 3. Review the required user roles or API permissions specified in the Vendor configuration field for each process to minimize security risks and optimize SaaS licenses. Note: For more information, see the [Minimal user permissions](https://www.servicenow.com/docs/cS0bvrJ9OdWO1IW6ALEM~w#integrate-with-jira-oauth "Integrate the Software Asset Management application with your Jira account using OAuth to authenticate ServiceNow requests.") table. 1. In the Download Subscription Subflow section, verify that the Subflow field is set to Jira Download Subscriptions. Note: The Download subscriptions check box is selected by default and you can't clear it. 2. In the Calculate Activity Subflow section, verify that the Subflow field is set to Jira Update User Activity. Note: The Download Activity check box is selected by default. If you clear it, the activity scheduled job SAM - Refresh \ Activity isn't created. In the Analyze user activity field, you can also select the date and time starting from when you want to analyze the user activity. By default, you can analyze user activity up to 60 days prior to the current date and view events performed by individual users from the time you create this profile. Note: Software Asset Management pulls the events from the time that you start analyzing user activity irrespective of the profile creation date. You can modify this value in the Last activity threshold field of your software reclamation rules. For more information, see [Review a software reclamation rule](https://www.servicenow.com/docs/QjHAOC5kmvypyG1Pph5iIQ "Use reclamation rules to cancel user subscriptions that have limited to no activity."). 3. In the Reclaim Subscription Subflow section, verify that the Subflow field is set to Jira Reclaim Subscription. Note: The Reclaim subscriptions check box is selected by default. If you don't want to reclaim subscriptions, you can clear this check box. If you clear it, the removal candidates are created but the reclaim subscription subflow isn't triggered or the reclamation process isn't initiated. {#create-integration-jira__substeps_rcm_pwm_vcc} 4. Select Save. A draft integration profile is created. The Connection \& Credential field appears and is automatically set to sn_jira_spoke.jira_subscription_activity_reclaim. Note: The automatically populated value in the Connection \& credential field changes based on the selection in the Download activity and Reclaim subscriptions check boxes.{#create-integration-jira__table_jkn_fry_r2c__entry__2} | Selection | Connection \& credential value | |-|-| | Both Download activity and Reclaim subscriptions are selected. | sn_jira_spoke.jira_subscription_activity_reclaim | | Only Download activity is selected. | sn_jira_spoke.jira_subscription_activity | | Only Reclaim subscriptions is selected. | sn_jira_spoke.jira_subscription_reclaim | | Both Download activity and Reclaim subscriptions aren't selected. | sn_jira_spoke.jira_subscription | [Table 3. Automatically populated Connection \& credential values based on the selection] {#create-integration-jira__table_jkn_fry_r2c} 5. Open the connection \& credential aliases record by selecting the preview icon ![]() next to the Connection \& Credential field and then selecting Open Record in the record preview. 6. On the Connection \& Credential Aliases form, select the Create New Connection \& Credential related link. 7. In the dialog box, fill in the fields. {#create-integration-jira__table_ujr_ps1_wmb_legacy__entry__2} | Field | Description | |-|-| | Connection Name | Name of the connection. | | Connection URL | Base URL for the Jira API. This field is automatically set to https://api.atlassian.com/ex/jira/<Cloud-ID>. | | The following fields are applicable for the Australia release, Software Asset Management - SaaS License Management (sn_sam_saas_int) store app version 17.4.0 or earlier. If you're on version 17.4.1 or later, these fields won't appear. || | OAuth Client ID | Client ID that is assigned to your Jira application. | | OAuth Client Secret | Client secret that is assigned to your Jira application. | | OAuth Redirect URL | URL of the OAuth provider that users are redirected to after authentication. This field populates automatically based and contains the URL of the ServiceNow instance that you specified in [Create an OAuth 2.0 integration in Jira account](https://www.servicenow.com/docs/cS0bvrJ9OdWO1IW6ALEM~w#create-oauth-int-jira "Create an OAuth 2.0 integration in the Atlassian Developer console to authenticate the requests."). | [Table 4. Create Connection and Credential dialog box] {#create-integration-jira__table_ujr_ps1_wmb_legacy} 8. Select Create and Get OAuth Token. Note: For the role required to perform this step, refer to the [Minimal user permissions](https://www.servicenow.com/docs/cS0bvrJ9OdWO1IW6ALEM~w#integrate-with-jira-oauth "Integrate the Software Asset Management application with your Jira account using OAuth to authenticate ServiceNow requests.") table. 9. When the dialog box appears, grant permission to the Jira application. The dialog box closes and you automatically return to the Connection \& Credential Aliases form. 10. On your ServiceNow instance, specify the groups that have access to Jira products. By specifying these groups on your ServiceNow instance, you can retrieve data and manage licenses for only the users within these groups. 1. In a new tab, open the [Atlassian Administration portal](https://admin.atlassian.com/). 2. Log in to your site admin account. 3. Select the Select button against the required organization. 4. Select the Products tab. 5. On the Products page, select Manage product on the Jira product row. 6. View the list of groups that have access to Jira Software. Secure this information for later use. 7. Return to your ServiceNow instance and navigate to JiraJira Groups. 8. On the Jira Groups form, select the Add Groups related link. The Add Jira Groups dialog box opens. 9. Select the Connection \& Credential that was set on the integration profile. 10. In the Available list, select the groups that have access to Jira products. Tip: The Available list includes all groups that are associated with your Atlassian account. Select only the groups that have access to Jira products. 11. Select the right arrow button to move the groups from the Available list to the Selected list. 12. Select OK. {#create-integration-jira__substeps_jtp_5sk_n4b} 11. On the integration profile form, select Validate Connection to verify the connection and credential details of this integration. Validating the connection verifies the Download Subscriptions and Calculate Activity APIs, but not the Reclaim Subscriptions APIs. 12. After the connection is verified, select Publish. 13. In the Publish Confirmation dialog box, select OK. Note: If you clear the Download Activity check box after the integration profile is published, you must revalidate the connections and then republish the integration profile because the following events occur: * The Status field on the integration profile form changes to Draft. * The Validate connection button shows up on the form. * The current SAM - Refresh \ Activity job gets deleted. {#create-integration-jira__ul_adf_2v3_ddc} ### What to do next After the integration connects, your ServiceNow instance automatically creates software models, reclamation rules, and software subscriptions that are refreshed daily. After creating an integration profile, view information about the profile in the Software Asset Workspace by navigating to License operationsUser subscriptionDirect integration profiles. You can select an integration profile to view the following related lists. If all of the following related lists aren't visible for an integration profile in the default view, you can select the custom integration view from the Details tab: * Software Models * Unrecognized Subscription Identifiers * Scheduled Jobs * Scheduled Job Results * Software Subscriptions * Subscription Identifier Exclusion Rule * Subscription User Exclusion Rule {#create-integration-jira__ul_gxp_qfk_rfc} After creating an integration profile, you can define subscription exclusion rules to keep certain subscriptions from license cost calculations. For more information, see [Subscription exclusions for SaaS and SSO applications](https://www.servicenow.com/docs/kwS~TWLEZdf67e7UjappHg#subscription-exclusions "Define subscription exclusions for your SaaS and SSO applications to optimize your licensing costs by keeping the excluded subscriptions out of license cost calculations."). If you want to set up multiple integration profiles with unique connections, create child aliases to manage different configurations and settings for each integration profile. For more information, see [Create a child alias to set up multiple Jira integration profiles](https://www.servicenow.com/docs/LoiOTo8e3~AKiviKTX0ieQ "Create a child alias to set up multiple Jira integration profiles with unique connections and manage different configurations for each integration profile."). Review all automatically generated reclamation rules to reclaim user subscriptions. For more information, see [Review a software reclamation rule](https://www.servicenow.com/docs/QjHAOC5kmvypyG1Pph5iIQ "Use reclamation rules to cancel user subscriptions that have limited to no activity."). Create software entitlements for the automatically generated software models to track used software against owned software. * For more information on creating software entitlements in the Software Asset Management Core UI, see [Create entitlements in Software Asset Management Core UI](https://www.servicenow.com/docs/8ZR9KWQ1FY73pUmBw_wZRQ "Create entitlements in the Software Asset Management Core UI application to record your license details and allocate purchased software rights to users or devices."). * For more information on creating software entitlements in the Software Asset Workspace, see [Create entitlements in workspace](https://www.servicenow.com/docs/ZvL7kERffOGQ6dpBU_744w "Create entitlements in the Software Asset Workspace to enter your license details and allocate purchased software rights to users or devices."). * For more information on creating software entitlements using the Software Asset Management Playbook, see [Create entitlements using the guided walk-through](https://www.servicenow.com/docs/rw30KUYxwGuwCDdFtc0mOg "Use the guided walk-through playbook for a step-by-step process of creating entitlements."). {#create-integration-jira__ul_umf_bk3_tfc} Reconciliation also runs on your subscriptions as a scheduled job or on-demand. You can view your reconciliation results in the [License Workbench](https://www.servicenow.com/docs/K_GziLbR~smXeeWp0kcdNw "Review reconciliation results in a simplified workbench view.") (Software Asset Management classic application) or the [License usage view](https://www.servicenow.com/docs/Ct5YAvsPFESpnVaeLwu5_w "Use the license usage view as a single plane to understand the license position of all software products, remediate non-compliance, view reconciliation results, view, or add removal candidates, and view Software Asset Management related reports.") (Software Asset Workspace). Use these results to determine your license compliance position and to remediate any non-compliance. * For more information on running reconciliation in the Software Asset Management classic application, see [Run software reconciliation in Software Asset Management classic](https://www.servicenow.com/docs/Pic766RsbcGCoP1GsB_9RA "Reconciliation is run as a scheduled job (default is weekly), but you can also run reconciliation manually to reconcile software products in your environment on demand."). * For more information on running reconciliation in the Software Asset Workspace, see [Run software reconciliation in the workspace](https://www.servicenow.com/docs/SUHzxdFqMeO8rQemacW3sA "Reconciliation is run as a scheduled job (default is weekly), but you can also run reconciliation manually to reconcile software products in the Software Asset Workspace environment on-demand."). {#create-integration-jira__ul_glc_ck3_tfc} *[\>]: and then