Description

Starting with Bitbucket 5.5, you can use personal access tokens many CLI actions and REST API requests instead of using basic authentication with user and password. See Bitbucket Personal Access Tokens for more details. An access token can be specified on the token parameter on CLI actions related to repositories.

The CLI also supports actions for managing access tokens: add, remove, and getAccessTokenList.

From the UI, go to Manage account and Personal access tokens.

Permission Table

See the Atlassian documentation for the current information. Here is a snapshot of that with some additional information including the valid values for the permission parameter on addAccessToken.

	Project read - PROJECT_READ	Project write - PROJECT_WRITE	Project admin - PROJECT_ADMIN
Repository read REPO_READ	Pull and clone repositories
Repository write REPO_WRITE	Perform pull request actions  Push, pull, and clone repositories	Perform pull request actions  Push, pull, and clone repositories
Repository admin REPO_ADMIN	Perform pull request actions  Update repository settings and permissions  Push, pull, and clone repositories	Perform pull request actions  Update repository settings and permissions  Push, pull, and clone repositories	Perform pull request actions  Update repository settings and permissions  Update project settings and permissions  Push, pull, clone, and fork repositories  Create repositories

Examples

--action addAccessToken  --name "project-admin"  --permission "PROJECT_ADMIN, REPO_ADMIN"

Other Information

• BSERV-10482 - Create admin personal tokens for admin endpoints in Bitbucket Server REST API