Conversation
Service-account 2LO can mint 60-minute Bearer tokens and call the Atlassian API gateway, so Jira Cloud connections no longer require a user API token. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds Jira Cloud OAuth 2.0 client-credentials (2LO / service account) as a native connection option.
Jira Cloud service accounts authenticate with
grant_type=client_credentials, not Basic Auth or a user API token. Access tokens last ~60 minutes and API calls go throughhttps://api.atlassian.com/ex/jira/{cloudId}/rest/.This extends the existing Jira Cloud (Atlassian API Gateway) connection from #9024:
authMethod=AccessToken)authMethod=OAuth2) with Cloud ID, Client ID, and Client SecretThe plugin mints tokens in memory, sends
Authorization: Bearer, and remints on 401 during long collections.authMethod=OAuth2is handled inside the Jira plugin so coreMultiAuth(oneof=BasicAuth AccessToken AppKey) does not need to change.Test Connection maps remote 401/403 to HTTP 400 and includes Jira's error body (e.g.
scope does not match), so Config UI does not treat a bad Jira credential as a DevLake session expiry.Does this close any open issues?
Relates to #8822 (closed as stale; please reopen if you want this PR to close it).
Screenshots