Jira Cloud/Flexera integration

[Apryl Harris]

Hi Community,
Anyone integrate Flexera/Jira Cloud using the OAuth 2.0 method?

I have the instructions just wanted to know if you ran into any issues? If so, what were they and how did you resolve?

Thanks!

[Alexandre Pezzini]

Hi! Thank you for reaching out to the Atlassian Community.

Integrating Flexera with Jira Cloud via OAuth 2.0 is a common way to automate asset management and vulnerability tracking. While the process is generally straightforward, there are a few common "gotchas" that users often encounter during setup.

Common Issues & Resolutions

1. Missing offline_access Scope

   • The Issue: The integration works initially but fails after an hour (or whenever the access token expires).

   • The Resolution: Ensure you include the offline_access scope in your OAuth 2.0 configuration. This is required for Jira to issue a refresh token, allowing Flexera to maintain a long-term connection without requiring manual re-authorization.

2. Granular vs. Classic Scopes

   • The Issue: Flexera may require specific permissions to read or write to work items. If you only select "Classic" scopes, some newer Jira Cloud features might not be accessible.

   • The Resolution: Verify that you have enabled all necessary Granular scopes (e.g., read:jira-work, write:jira-work, read:issue-details:jira) in the Atlassian Developer Console for your app.

3. Redirect URI Mismatch

   • The Issue: You receive an "Invalid Redirect URI" error during the authorization handshake.

   • The Resolution: The Callback URL (Redirect URI) provided by Flexera must exactly match what is entered in the Atlassian Developer Console. Even a trailing slash (/) or a difference between http and https will cause the integration to fail.

4. User Permissions for the "Integration User"

   • The Issue: The OAuth connection is successful, but Flexera cannot see certain projects or update work items.

   • The Resolution: The Jira user account used to authorize the OAuth app must have the correct Space Permissions (e.g., "Create Work Items," "Edit Work Items") in every space Flexera needs to interact with. We recommend using a dedicated "Service Account" for this.

Quick Setup Checklist

• Developer Console: Create a new "OAuth 2.0 (3LO)" integration at Developer console.

• Scopes: Add offline_access plus the specific read and write scopes required for your Flexera module.

• Credentials: Copy the Client ID and Client Secret into Flexera.

• Authorization: Ensure you are logged into Jira as the intended service user when you click the "Authorize" button in Flexera.

If you run into specific error codes (like 401 Unauthorized or 403 Forbidden) after following your instructions, feel free to share them here!

Sources:

• I fail to get an OAuth 2.0 refresh token | Jira and Jira Service Management | Atlassian Support

• OAuth 2.0 (3LO) apps