Skip to main content

Bitbucket Connector Settings Reference

This topic provides settings and permissions for the Bitbucket Connector.


  • Before Harness syncs with your Git repo, it verifies all the connection settings in Harness. If Harness cannot establish a connection, it won't sync with your Git repo.

Harness supports both Cloud and Data Center (On-Prem) versions of Bitbucket. The following settings are applicable for both versions.


The unique name for this Connector.


See Entity Identifier Reference.


Text string.


See Tags Reference.

URL Type

Select one type:

  • Account: Connect to your entire Git account. This enables you to use one Connector for all repos in the account. If you select this, you must provide a repository name to test the connection.
  • Repository: Connect to one repo in the account.

Connection Type

The protocol to use for cloning and authentication. Select one type:

  • HTTPS: Requires a personal access token.
  • SSH: You must use a key in PEM format, not OpenSSH.
    To generate an SSHv2 key, use: ssh-keygen -t rsa -m PEM The rsa and -m PEM ensure the algorithm and that the key is PEM. Next, follow the prompts to create the PEM key. For more information, see the ssh-keygen man page.

Bitbucket Account URL

The URL for your Git repo. Make sure that it matches the Connection Type option you selected.

If the URL Type is Repository, enter the full URL for the repo.

If the URL Type is Account, enter the URL without the repo name. You will provide a repo name when you use the Connector.

If the Connection Type is HTTP, enter the URL in the format<userName>/<repoName>.git.


Bitbucket repos with read-only access also require a username and password.You can use a password for HTTPS credentials.

If you selected SSH as the connection protocol, you must add the SSH Key for use with the connection. 

If you log into Bitbucket using a Google account, you can create an application password in Bitbucket to use with Harness. For steps on this, see App passwords from Atlassian.


The username for the account.


A Harness Encrypted Text secret for the credentials of your Bitbucket user account.

If you have set up Two-Factor Authentication in your Bitbucket account, you need to generate a personal access token in your repo and enter that token in the Password/Token field.


If you selected SSH as the connection protocol, you must add the SSH Key for use with the connection as a Harness Encrypted File secret. For steps to create an SSH Key, see Add new SSH Key.

Enable API access

This option is required for using Git-based triggers, Webhook management, and updating Git statuses. If you are using Harness Git Experience, you will need to use this setting.

API Authentication


The username for the account.

You must enter a plain-text username or a username secret for both Authentication and API Authentication. You cannot use a plain-text password for one field and a secret for the other.

Personal Access Token

A Harness Encrypted Text secret for the App password of your Bitbucket user account.