Skip to main content

Capabilities

Provisioning for Accounts means creating and deleting Bitbucket users. It requires basic auth (see below); an HTTP access token can’t create or delete accounts.

Gather Bitbucket Data Center credentials

Configuring the connector requires you to pass in credentials generated in Bitbucket Data Center. Gather these credentials before you move on.

Create an HTTP token

1
In Bitbucket, click your profile in the top right corner of the screen and navigate to Manage account > HTTP access tokens.
2
Click Create token.
3
Give the token a name, such as “C1”.
4
In the Permissions section of the page, select these permissions:
  • Project: Admin
  • Repository: Admin
This token is enough to sync data and provision group/project/repo access, but not to create or delete Bitbucket user accounts.
Account provisioning (creating and deleting users) is not supported when the connector is configured with an HTTP access token. To provision accounts, configure the connector with a username and password for a user with the global Administrator (ADMIN) or System Administrator (SYS_ADMIN) permission. You can’t configure both a token and a username/password.
5
Click Create.
6
Your new token is shown. Carefully copy and save the token.
Done. Next, move on to the connector configuration instructions.

(Optional) Credentials for account provisioning

Account provisioning (creating and deleting Bitbucket users) requires a username and password for a user with the global Administrator (ADMIN) or System Administrator (SYS_ADMIN) permission - an HTTP access token can’t be used for this. A token and a username/password are mutually exclusive; the connector rejects configuring both at once. Token users still need BATON_PROVISIONING enabled to provision group/project/repo access. When creating an account, you can optionally set Add to default group, which adds the new user to Bitbucket’s default group. The default group controls the user’s initial permissions and ability to log in; it defaults to off. Deprovisioning an account deletes the Bitbucket user. The connector has no disable action. Users managed by an external user directory (such as LDAP or Crowd) can’t be deleted through the Bitbucket API; deleting one returns the error reported by Bitbucket.

Configure the Bitbucket Data Center connector

To complete this task, you’ll need:
  • The Connector Administrator or Super Administrator role in C1
  • Access to the set of Bitbucket Data Center credentials generated by following the instructions above
Follow these instructions to use a built-in, no-code connector hosted by C1.Cloud-hosted connector not currently available.