Managing access tokens
Estimated reading time: 2 minutes
Docker Hub lets you create personal access tokens as alternatives to your password. You can use tokens to access Hub images from the Docker CLI.
Using personal access tokens provides some advantages over a password:
- You can investigate when an access token was used last, and disable or delete it if you find any suspicious activity.
- When logged in with an access token, you can’t perform any admin activity on the account, including changing the password.
Access tokens are also useful in building integrations, since you can issue multiple tokens – one for each integration – and revoke them at any time.
Note: If you have two-factor authentication (2FA) enabled on your account, you must create at least one personal access token. Otherwise, you will be unable to log in to your account from the Docker CLI.
Create an access token
You can create as many tokens as you need.
Log in to hub.docker.com.
Click on your username in the top right corner and select Account Settings.
Select Security > New Access Token.
Add a description for your token. Use something that indicates where the token is going to be used, or set a purpose for the token.
Copy the token that appears on the screen. Make sure you do this now: once you close this prompt, Docker will never show the token again.
Treat access tokens like your password and keep them secret. Store your tokens securely (for example, in a credential manager).
Modify existing tokens
You can rename, deactivate, or delete a token as needed.
Access your tokens under Account Settings > Security.
Select a token and click Delete or Edit, or use the menu on the far right of a token row to bring up the edit screen. You can also select multiple tokens to delete them all once.
Use an access token
You can use an access token anywhere that requires your Docker Hub password.
When logging in from your Docker CLI client (
docker login --username <username>),
omit the password in the login command. When you’re prompted for
a password, enter your token instead.
If you have 2FA enabled, you must use a personal access token when logging in from the Docker CLI. If you don’t have it enabled, this is an optional (but more secure) method of authentication.docker hub, hub, security, PAT, personal access token