Managing HTTP access tokens
Administer Bitbucket Data Center
- Users and groups
- Advanced repository management
- External user directories
- Global permissions
- Setting up your mail server
- Integrate with Atlassian applications
- Connect Bitbucket to an external database
- Migrating Bitbucket Data Center to another server
- Migrate Bitbucket Server from Windows to Linux
- Run Bitbucket in AWS
- Specify the Bitbucket base URL
- Configuring the application navigator
- Managing apps
- View and configure the audit log
- Monitor security threats
- Update your license key
- Configuration properties
- Change Bitbucket's context path
- Data recovery and backups
- Disable HTTP(S) access to Git repositories
- Mirrors
- Bitbucket Mesh
- Export and import projects and repositories
- Git Large File Storage
- Git Virtual File System (GVFS)
- Enable SSH access to Git repositories
- Signed system commits
- Secret scanning
- Use diff transcoding
- Change the port Bitbucket listens on
- Lockout recovery process
- Configure secure administrator sessions (websudo)
- Proxy and secure Bitbucket
- High availability for Bitbucket
- Diagnostics for third-party apps
- Enabling JMX counters for performance monitoring
- Bitbucket guardrails
- Enable debug logging
- Scaling Bitbucket Data Center
- Add a shortcut link to a repository
- Administer code search
- Adding additional storage for your repository data
- Add a system-wide announcement banner
- Configuring Project links across Applications
- Improving instance stability with rate limiting
- Use a CDN with Atlassian Data Center applications
- Managing HTTP access tokens
- Manage keys and tokens
- Link to other applications
- Setting a system-wide default branch name
- Automatically decline inactive pull requests
- Monitor application performance
- Secured secrets by default
- Secure Bitbucket configuration properties
- Data pipeline
On this page
Related content
- HTTP access tokens
- Managing keys
- How to bypass Verify Committer Hook in Bitbucket Data Center
- An error "You are not permitted to access this resource" appears in Bitbucket Data Center while creating a fork repository into a different project via the API
- Creating projects
- How to renew personal access tokens via REST API's in Bitbucket Server
- OAuth 2.0 provider system properties
- How to allow public access to a repository via the REST API in Bitbucket Server
- Global permissions
- Manage keys and tokens
Project and repository administrators can create HTTP access tokens for their projects and repositories. Users can create personal HTTP access tokens and use them in place of passwords for Git over HTTPS, or to authenticate when using the Bitbucket Data Center REST API. As an administrator, you can edit and revoke tokens, and set global token settings.
Editing and deleting tokens
As an administrator, you can’t create tokens for users. However, once a user has created a token, you can edit or delete it.
To edit or delete a personal HTTP token:
Go to
> Users.
Search for the user and click on them.
Open the HTTP access tokens tab.
Select Edit or Delete.
To edit or delete a project or repository's HTTP token:
- From either the Project or Repository settings, select HTTP access tokens.
- Select Edit or Delete.
Selecting Edit will allow you to change a token’s name or its permissions. If it has an expiry date, however, you will not be able to modify it. Once a token’s expiry date has been set, it can’t be changed.
Require token expiry
By default, when a user is creating a personal access token, they can choose whether they want it to expire. As a system administrator, for added security you can make setting a token expiry a requirement.
To require token expiry:
Go to
> Keys and tokens (under System).
Select Yes for Automatic expiry.
Enter the HTTP access token expiry (in days).
Select Save.
Related content
- HTTP access tokens
- Managing keys
- How to bypass Verify Committer Hook in Bitbucket Data Center
- An error "You are not permitted to access this resource" appears in Bitbucket Data Center while creating a fork repository into a different project via the API
- Creating projects
- How to renew personal access tokens via REST API's in Bitbucket Server
- OAuth 2.0 provider system properties
- How to allow public access to a repository via the REST API in Bitbucket Server
- Global permissions
- Manage keys and tokens