> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm/registration/version-control-repository/bitbucket/configuring-bitbucket-token-authentication-and-email-support.md).
# Configuring Bitbucket Token Authentication and Email Support
### Introduction
Bitbucket is deprecating App Password authentication effective **June 9, 2026**. To ensure uninterrupted connectivity and support for Bitbucket API operations, AutoRABIT supports Token-based authentication and provides an Email Address field for Bitbucket credentials.
This guide explains how to configure and update Bitbucket credentials in AutoRABIT.
***
### Prerequisites
Before proceeding, ensure that:
* You have access to your Bitbucket account.
* A Bitbucket App Token has been generated.
* You know the email address associated with your Bitbucket account.
***
### When Is an Email Address Required?
An email address is required for Bitbucket API-based operations such as:
* Pull Request Creation
* Other Bitbucket REST API operations
The email address is not required for Git operations such as:
* Clone
* Fetch
* Push
***
### Configuring a New Bitbucket Credential
#### Classic UI
1. Navigate to **Settings → Credentials**.
2. Click **Create Credential**.
3. Select **Bitbucket**.
4. Enter:
* Username
* Token
* Email Address (Optional)
5. Save the credential.
***
### Updating an Existing Bitbucket Credential
1. Navigate to **Settings → Credentials**.
2. Locate the Bitbucket credential.
3. Click **Edit**.
4. Enter or update the **Email Address** field.
5. Save the changes.
***
### Repository Registration
When registering a Bitbucket repository:
1. Select the Bitbucket credential.
2. Verify that the credential contains:
* Username
* Token
* Email Address (recommended)
3. Complete repository registration.
***
### Best Practices
* Migrate from App Passwords to Tokens before June 9, 2026.
* Configure an Email Address for all Bitbucket credentials used for Pull Request workflows.
* Periodically review and update repository credentials.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://knowledgebase.autorabit.com/product-guides/arm/registration/version-control-repository/bitbucket/configuring-bitbucket-token-authentication-and-email-support.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
