New connector setup for Jira and Confluence

Note:This enhancement is available with Flexera One SaaS Management.

Flexera One SaaS Management is introducing a major improvement to the way Jira and Confluence connectors are configured, making the process simpler and more secure. Previously, setting up these connectors required using two different authentication methods—OAuth 2.0 for most API calls and Basic Authentication for specific endpoints, such as retrieving the number of seats in Jira. This approach was necessary because, at the time, Atlassian only supported Basic Auth for certain data. However, it added complexity for users and increased security risks.

Atlassian has since introduced API tokens with granular scopes, providing a modern and secure way to access all required endpoints. With this update, Basic Authentication is being removed from the Jira connector. Users will now have two secure options for authorization: OAuth 2.0 or API Token with Scopes. The API token method requires creating a service account with appropriate permissions and generating a token, but it offers a streamlined and secure setup experience. For Confluence, Basic Auth remains necessary for seat-related APIs because these endpoints are not yet officially documented. Users can choose to skip this step and manually enter seat counts if preferred, and we’ve already submitted a request to Atlassian to make these APIs official.

This change delivers significant benefits: a simplified setup process, enhanced security by eliminating Basic Auth for Jira, reduced risk of configuration errors, and alignment with Atlassian’s latest standards. Overall, it ensures a better experience for customers and prepares the connectors for future improvements.