Personal Access Tokens

Personal access tokens function similar to session tokens and can be used by integrations to authenticate against the REST API. It is the most commonly used type of token for integrations.

You can create a personal access token and use it in place of a password when performing Git operations over HTTPS with Git on the command line or the API.

A personal access token is required to authenticate to Git account in the following situations:

When you're using two-factor authentication
To access protected content in an organization that uses SAML single sign-on (SSO). Tokens used with organizations that use SAML SSO must be authorized.

Creating a Personal Access Token

Create a personal access token in GitHub - https://help.github.com/en/articles/creating-a-personal-access-token-for-the-command-line
Create a personal access token in GitLab - https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html
Create a personal access token in Bitbucket

Data Center and Server:

- https://confluence.atlassian.com/bitbucketserver/personal-access-tokens-939515499.html

For Bitbucket Cloud you can use:

App passwords or OAuth.

Create a personal access token in Beanstalk - https://support.beanstalkapp.com/article/901-2-step-login-verification
Create a personal access token in Azure DevOps - https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=preview-page (Choose “All accessible organizations” option in “Organization”. The scope of access associated with this token choose “Full access”)