squatboy opened a new issue, #8822: URL: https://github.com/apache/incubator-devlake/issues/8822
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar feature requirement. ### Use case As a platform/DevOps engineer, I want Apache DevLake's Jira plugin to support OAuth 2.0-based service account (non-human account) authentication, so that our organization can integrate Jira without relying on user API tokens or personal credentials. In our environment, Jira integrations are expected to use a service account / non-human account with OAuth 2.0-based authentication. ### Description DevLake's Jira connector appears to support token-based or username/password-style authentication flows, but it does not appear to provide a native option for OAuth 2.0-based service account authentication. We would like DevLake to support this authentication model for the Jira connector. From a user perspective, the feature would ideally allow: - configuring Jira connections with OAuth 2.0-based service account credentials - using a non-human/service account for Jira data collection - handling the necessary access token flow in the Jira connector itself instead of requiring an external authentication proxy or workaround This would help organizations that: - do not want integrations tied to individual user accounts - require centrally managed service-account credentials - use OAuth 2.0-based authentication for internal system-to-system integrations ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
