Skip to content

Replace Bitbucket app passwords with API tokens #787

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Replace Bitbucket app passwords with API tokens #787

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions platform-cloud/docs/git/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,11 @@ To connect to a private [Gitea](https://gitea.io/) repository, use your Gitea us

### Bitbucket

To connect to a private BitBucket repository, see the [BitBucket documentation](https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/) to learn how to create a BitBucket App password. Then, create a new credential in Seqera with these steps:
To connect to a private BitBucket repository, see the [BitBucket documentation](https://support.atlassian.com/bitbucket-cloud/docs/api-tokens/) to learn how to create a BitBucket API token. Then, create a new credential in Seqera with these steps:

:::warning
API tokens are the replacement for [app passwords](https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/), which cannot be created starting from September 9, 2025 and will be phased out June 9, 2026. They are still supported but not recommended. See the [transition notice](https://www.atlassian.com/blog/bitbucket/bitbucket-cloud-transitions-to-api-tokens-enhancing-security-with-app-password-deprecation) for more information.
:::

**Create BitBucket credentials**

Expand All @@ -175,7 +179,7 @@ To connect to a private BitBucket repository, see the [BitBucket documentation](

3. Select _BitBucket_ as the **Provider**.

4. Enter your **Username** and **Password**.
4. Enter your **Username** (email) and **Token**.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When using API tokens, the username is the account email. However, when using app passwords the username is the account nickname. Any suggestions on how to express it better, @llewellyn-sl?


5. Enter the **Repository base URL** (recommended). This option can be used to apply the credentials to a specific repository, e.g., `https://bitbucket.org/seqeralabs`.

Expand Down