Jira Connector Service Account Support Added
Overview
We’ve added service‑account authentication options to the Jira Software connector in Fusion. You can now create Jira connections using a service account API token or service account OAuth 2. These options let teams build reliable, machine‑level integrations that aren’t tied to an individual user account.
What’s new
- Service account — API token: Authenticate the Jira connector with a service account identity using an API token.
- Service account — OAuth 2: Authenticate via OAuth 2 using a registered OAuth client tied to a Jira service account.
- Both connection types appear alongside existing user‑based connection options in the Jira connector dialog.
Why this matters
- Stability — Service accounts reduce disruptions caused by employee changes or credential expirations.
- Auditability — Activities generated by connector operations are scoped to a dedicated service identity, making logging and compliance easier.
- Enterprise fit — Supports machine‑to‑machine integration patterns and centralized credential governance common in larger organizations.
How to get started
- Open Fusion → Connections > Create Connection → choose Jira Software.
- From the Connection Type dropdown select either:
- Service account — API token and enter the service account identifier and API token.
- Service account — OAuth 2 and follow the OAuth client flow (you may need to register an OAuth app in Atlassian and provide client ID/secret and callback URL).
- Save the connection and run test actions (create issue, update issue, search) to validate permissions.
Permissions and security
- Service account connections act with the permissions assigned to the service account in Jira — they cannot exceed those rights.
- When using OAuth 2, grant only the scopes required for your scenarios.
- Secrets (API tokens, client secrets) are stored securely and are not exposed in Fusion UI readouts; only connection metadata and status are visible.
Admin checklist
- Create a dedicated Jira service account and grant the minimum required project/issue permissions.
- Decide between API token (simple server‑to‑server) and OAuth 2 (centralized app governance and finer scope control) based on your security policy.
Troubleshooting (quick)
- Actions return permission errors: Review the service account’s Jira project roles and issue permissions and adjust as needed.
Where to find documentation
- Jira Software connector — Fusion reference (Experience League)
- Atlassian: Understand service accounts
Feedback and support
If you have questions, encounter issues, or want enhancements (for example, automated token rotation hooks or role‑based connection templates), please:
- Post in the Experience League Community thread for the Jira connector
- Open a support ticket via the Admin Console Support portal for access or migration help
- Include connection metadata and example error messages when reporting connector errors to help us troubleshoot faster
We’re excited to deliver more robust authentication choices for Jira integrations. Try the new service‑account connection types and tell us how they work for your automations.