Authenticate with Bitbucket OAuth
Adds your Bitbucket credentials to the .netrc file. Bitbucket Cloud is removing app passwords — use a Bitbucket API token instead.
Adds your Bitbucket credentials to the .netrc file. Bitbucket Cloud is removing app passwords — use a Bitbucket API token instead.
This Step adds your Bitbucket authentication configuration to the .netrc file, so that HTTPS Git operations (clone and push) and REST API calls to Bitbucket are authenticated.
Please note that if you already have a .netrc file, the Step will create a backup of the original, and appends the configs to the current one.
Bitbucket Cloud is removing app passwords. Creating new app passwords is already disabled, and existing app passwords stop working during the brownouts that begin on 2026-06-09, with full removal on 2026-07-28 (see Atlassian's announcement). Because this Step writes the credential into .netrc, and that credential is used for HTTPS Git operations — including push and other write access — and for REST API calls, any setup that relies on an app password will stop working once they are removed.
Use a Bitbucket API token instead. Create one by following the Bitbucket API token instructions and enter it in the App password or API token input below. As an alternative that is unaffected by this change, you can authenticate over SSH with the Activate SSH key Step.
App passwords accepted the Bitbucket username for both bitbucket.org (Git over HTTPS) and api.bitbucket.org (REST API), so a single .netrc entry covered both hosts. API tokens authenticate the two hosts with different logins:
bitbucket.org (Git over HTTPS) uses your Bitbucket username together with the API token.api.bitbucket.org (REST API) uses your Atlassian account email together with the API token.To support both, the Step writes a separate .netrc entry per host: the Bitbucket username input is used for the Git host, and the optional Atlassian account email input is used for the REST host. Leave the email empty if you only run Git operations — the api.bitbucket.org entry is then skipped, so existing configurations keep working unchanged.
api.bitbucket.org, add your Atlassian account email.
