This Epic was promoted from the issue https://gitlab.com/gitlab-org/gitlab/-/issues/296989. ### Release notes So far, users on Jira Data Server and Jira Server could authenticate with [Jira issue integration](https://docs.gitlab.com/ee/integration/jira/configure.html) with username and password. Personal access tokens (PATs) are a safe alternative to using username and password and [Jira Data Server and Jira Server from version 8.14 support this authentication method](https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html). We are adding support for PATs in our Jira issue integration. ### Proposal In JIRA Server 8.14 and Confluence Server 7.9 atlassian has added tokens as a way to authenticate to the REST API. Much better then people using their company wide ldap password for this (and storing it in places). **Describe the solution you'd like** I think we should support this new authentication method as JIRA Datacenter will also use it and stay beyond 2024. And basic authentication with passwords will be deprecated at some point by atlassian. **Describe alternatives you've considered** Add support for https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html **Additional context** Please note these personal access tokens are slightly different from the JIRA Cloud api tokens. Cloud: `curl -H "Authorization: Basic <base64(<username>:<yourToken>>)" https://{jiraBaseUrl}/rest/api/` Server: `curl -H "Authorization: Bearer <yourToken>" https://{jiraBaseUrl}/rest/api/` ### Customer Impact This affects our [Jira issue integration](https://docs.gitlab.com/ee/integration/jira/configure.html). - https://gitlab.my.salesforce.com/0014M00001wUepD | PubSec, 200 seats - https://gitlab.my.salesforce.com/0064M00000Z8Arb | Prospect, Jira DataCenter - https://gitlab.my.salesforce.com/0016100001TXKFqAAP / [Support Issue](https://gitlab.zendesk.com/agent/tickets/245553) ~"GitLab Premium", 10,020 seats - https://gitlab.my.salesforce.com/0016100001edds0AAA / [Support Issue](https://gitlab.zendesk.com/agent/tickets/266220) ~"GitLab Starter", 20 seats - https://gitlab.my.salesforce.com/0016100001StYQeAAN | ~"GitLab Premium", 55 seats About [5.6M projects ](https://app.periscopedata.com/app/gitlab/822206/Manage:Integrations-Usage?widget=12463560&udv=0)leverage an integration with Self-managed Jira, whether directly or by inheriting the integration settings, which could all benefit from PATs as an alternative. <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> ### Designs | Cloud | Server | PAT | | ------ | ------ | ------ | |  |  |  | - :frame_photo: [Figma project](https://www.figma.com/file/eaSN9OEQVMwwi0Vvq0Iugl/JIRA%3A-Support-Personal-Access-Tokens-!8222?node-id=1906%3A432&t=e4u5BLWvo41MYqZQ-1) - :computer: [Figma prototype](https://www.figma.com/proto/eaSN9OEQVMwwi0Vvq0Iugl/JIRA%3A-Support-Personal-Access-Tokens-!8222?page-id=1%3A2&node-id=1906%3A432&viewport=738%2C777%2C0.63&scaling=min-zoom&starting-point-node-id=1906%3A432)