Skip to content
Zide Zide Zide

Bitbucket authentication

Zide connects to Bitbucket Cloud to provide pull requests, Pipelines, Downloads, and Bitbucket Overview. Bitbucket Cloud has no issue tracking or releases.

Zide authenticates with a Bitbucket API token and the email of your Atlassian account.

Create an API token

Create an API token with scopes on your Atlassian account. Choose Bitbucket as the app. For the steps, see Create an API token in the Bitbucket Cloud documentation.

Select the scopes that the Connect to Bitbucket Cloud dialog lists. To make a repository public or private from the Bitbucket Overview tab, the token must also grant admin on Repositories. Zide works without this permission; only the visibility change needs it.

Bitbucket shows the token only once. Copy it before you close the page.

Connect your account

To connect your Bitbucket account, complete the following steps.

  1. Open Settings.
  2. In Settings, click Git Accounts.
  3. In Git Accounts, click Connect account.
  4. In the Connect a Git hosting account dialog, click Bitbucket Cloud.
  5. In the Connect to Bitbucket Cloud dialog, enter your email in the Atlassian account email field.
  6. Enter your API token in the API Token field. To open the Atlassian page where you create tokens, click Open Atlassian API token settings.
  7. Click Connect. Zide is now connected to your Bitbucket account.

Zide validates the token format and checks it against the Bitbucket API.

Tokens

Tokens are stored securely in the native keychain of the following operating systems:

  • Windows: Data Protection API
  • macOS: Keychain
  • Linux: Secret Service (GNOME Keyring, KWallet, KeePassXC, or another libsecret provider)

Account metadata such as the username, avatar URL, and auth method is stored in Zide’s local SQLite database. Tokens remain in the operating system’s secure credential store.

API tokens expire. When you create a token, you set an expiry date from 1 day to 1 year later. For details, see Manage API tokens for your Atlassian account. When the token expires or you revoke it, create a new token. Then, in Settings > Git Accounts, click Reconnect for the account and enter the new token.

If Zide shows that the account doesn’t have permission to read a list, such as Reviewers, check the token’s scopes. If the token does not have every scope that the Connect to Bitbucket Cloud dialog lists, create a new token with all of them and click Reconnect.