Skip to content
Zide Zide

Bitbucket authentication

Zide connects to Bitbucket to provide issue tracking, pull requests, releases, actions, and other features.

You can authenticate Zide with a personal access token.

Authenticate with a personal access token

To authenticate with a personal access token, complete the following steps.

  1. Click File > Settings.
  2. In Settings, click Providers.
  3. In Providers, click Add Account.
  4. In the Add Account dialog, click Bitbucket Cloud.
  5. In the Connect to Bitbucket Cloud dialog, enter your account email in the Atlassian account email field.
  6. Enter your Atlassian API Token in the API Token field. To generate a personal access token, see the Create an API Token Bitbucket documentation.
  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 or pass

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.

Personal access tokens do not expire unless they are revoked manually on Bitbucket.

Reconnect required

An account’s token lives in the OS keychain while the rest of the account lives in Zide’s database. If the keychain is unavailable when you connect an account (on Linux, a locked or stopped Secret Service is the usual cause), Zide shows the keychain error and does not add the account. Reconnecting an existing account the same way leaves that account exactly as it was, still using its previous token.

If a token is removed from the keychain outside Zide, the account is marked Reconnect required in Settings > Providers. Zide does not authenticate with an account in that state; click Reconnect to store a working token again.