Git Integration for Jira Self-Managed (Data Center/Server) Documentation

Contact Support
GitKraken Status  

New GitLab v10+ authentication

GitLab v10+ stopped accepting username/password credentials for API access and will only recognize Personal Access Tokens (PAT) and OAuth authentications. Service users are strongly advised to switch from using username/password for and newer versions of GitLab Server (CE/EE) to using Personal Access Tokens.

For GitLab Server service users, they won’t see the issue until they upgrade their GitLab Servers to version 10 and higher. Git Integration for Jira app offers pre-v10 GitLab Server users as a Legacy connection option.

To access a Git repository over HTTP, use the username as the username and the PAT for the password.

To pass the private access token (for example: XpigzF1JxMnAZ7mn9qgN) to an API call with

curl --header "Private-Token: XpigzF1JxMnAZ7mn9qgN"


For more information on GitLab personal access token, see GitLab: Personal Access Token.


Prev: Setup GitLab Server to respond to incoming network API calls

Next: General settings – Improving Jira performance


More related articles on Git for Jira administrators

Setup GitLab Server to respond to incoming network API calls

New GitLab v10+ authentication (this page)

General settings: Improving Jira performance

Adding a repository hosted on Windows Servers or Windows Network Share (Admins)

Setting up repository root not located in Jira Home directory (Admins)

Reindex API to trigger indexing

Recommended reindex interval setting

Setting up web linking

Setting up webhooks

Increasing timeout threshold for large repositories while doing a Git pull

Working with Tracked folders

Recommended upgrade method for Git Integration for Jira

Discard cloned files in Jira Home directory (General setting)

Have feedback about this article? Did we miss something? Let us know!
On this page