Skip to main content

Authentication

The plugin requires authentication to access the Bitbucket API. The available methods depend on whether you are connecting to Bitbucket Cloud or Bitbucket Data Center.

OAuth2 (Cloud)​

  1. When prompted to authenticate, your default browser opens a Bitbucket authorization page.
  2. Log in to your Bitbucket account (if not already logged in) and grant access to the plugin.
  3. After authorization, the browser redirects back to the IDE and the plugin stores your credentials automatically.

The plugin automatically refreshes your OAuth2 token in the background. If the refresh fails, you will be prompted to re-authenticate.

HTTP Access Token (Data Center)​

  1. In Bitbucket Data Center, go to your Profile → Manage Account → HTTP access tokens.
  2. Click Create token, give it a name, and grant it Repository read and Pull request write permissions (at minimum).
  3. Copy the generated token.
  4. When the plugin prompts for authentication, select HTTP Access Token and paste the token.

Username and Password (Data Center)​

Enter your Bitbucket Data Center username and password when prompted. This method uses HTTP Basic authentication.

note

HTTP Access Tokens are recommended over username and password because they can be scoped to specific permissions and revoked independently.

Changing Account​

To switch to a different Bitbucket account, use the Change Account action in the Bitbucket Pull Requests tool window toolbar. This opens the login dialog where you can enter new credentials.

Default Account​

When logging in, you can check Use this account for other projects by default. This makes the current credentials the default for any new project that connects to the same Bitbucket instance.

Credential Storage​

All credentials are stored securely in the IDE's built-in credential store (Settings | Appearance & Behavior | System Settings | Passwords). No passwords or tokens are stored in plain text or in project files.