- Task
- Version · 6.0.2
- Manage
Create a personal access token
Last updated: November 17, 2026
Create a personal access token when you want to run Liquibase on your own machine as yourself, for example to run checks with a policy assignment.
Before you begin
Personal access tokens must be turned on for your workspace. They are on unless an administrator has turned them off.
You must have fewer than 10 active personal access tokens. If you have 10, revoke one you no longer use first.
Procedure
Open your personal access tokens
Sign in to Liquibase Secure server, select your name in the top-right corner, and select Personal access tokens.
The page lists the tokens you own, with each one's name, prefix and status, and when it was created, last used and expires. Every user manages their own tokens here, administrators included.
Name the token
Select Create token, and enter a name of up to 32 characters. Name it after where you will use it, such as your machine or project, so you can tell your tokens apart when you revoke one later.
Names do not have to be unique. If you already have a token with the same name, the console warns you, and you can still continue.
Choose when the token expires
Choose a lifetime of 30, 60 or 90 days. The longest lifetime your workspace allows is selected by default, and the date the token will expire is shown before you create it. Then select Create token.
Note: If an administrator has lowered the workspace maximum, the longer lifetimes are not offered, and the console tells you what the maximum is.
Copy the token value
The token's value is shown once, right after you create it. Select Copy token now and keep the value somewhere safe, such as a password manager, then select Done. After you close the dialog, nobody can see the value again, administrators included. If you lose it, revoke the token and create another.
Note: Treat the value like a password. Anyone who has it can act as you in Liquibase Secure server until the token expires or is revoked.
Use the token with Liquibase
Give Liquibase the token value in liquibase.platform.apiKey, together with your server's API URL in liquibase.platform.apiUrl, and set liquibase.platform.enabled to true. You only need one place for them, either your liquibase.properties file or environment variables. Keep the token out of any file you commit to a shared repository.
If you use a liquibase.properties file, add these lines. Be sure to:
Replace
your_server_api_urlwith your Liquibase Secure server API URL, as described in Configure operation reporting. For example,http://localhost:3000/apiReplace
your_tokenwith the value you copied in step 4. It starts withliq_.
liquibase.platform.enabled=true
liquibase.platform.apiUrl=your_server_api_url
liquibase.platform.apiKey=your_tokenIf you use environment variables, set these instead, with the same values.
Liquibase now authenticates as you, with your access.
Check that the token works
From the folder with your liquibase.properties file, or the terminal where you set the environment variables, run checks run. It runs your policy checks locally and doesn't change your database. Before it does, it signs in to Liquibase Secure server with your token.
liquibase checks runThe token works if the output includes this line, with your email and your token's prefix:
[LB-PLATFORM] Authenticated as your_email (personal access token liq_a1b2c3…)The output also says the results were not sent to Change Intelligence. That's expected, because personal access tokens can't send operation data.
If you don't see the line, check the output:
No
[LB-PLATFORM]lines at all:liquibase.platform.enabledisn't set totrue."rejected the request … with 401":
liquibase.platform.apiKeydoesn't hold the whole token value. The command still finishes, so check the output, not the exit code.A message that the token was revoked, has expired or is suspended: see Troubleshooting in Run checks with a policy assignment.
Note: If the folder has no checks settings file, Liquibase creates liquibase.checks-settings.conf there.