Note: These steps refer to the Supervisor Web UI introduced in V13.0.0. Personal access tokens are under Platform > Settings > Supervisor. If your device shows the earlier Web UI, without the Platform sidebar, this section is not available.
We recommend a personal access token when a script or integration needs to sign in to the device without using the Web UI password. You create the token on the device and download it before you leave the page. The full token is shown only once.
A token created here signs in to that device. To call LiveEdge® Cloud, create the token in LiveEdge® Cloud Control. See Generating a LiveEdge® Cloud Personal Access Token (PAT).
Generate a personal access token
Under Personal access tokens on the Supervisor tab, select Create token. Give the token a name you will recognize, choose the role it should have, and choose when it should expire.
- Browse to the device's Web UI and sign in if prompted. When sign-in is on, use an administrator account.
- In the left sidebar, expand Platform and select Settings, then open the Supervisor tab.
- Under Personal access tokens, select Create token. If you have not created one yet, the section says No personal access tokens.
- Enter a Name.
- Set Role to Viewer, Operator, or Admin. Viewer is selected by default. Choose the role that matches what the integration needs to do.
- Set Expiration to 30 days, 90 days, 365 days, or No expiration. 90 days is selected by default. We recommend keeping an expiration, so a token that is no longer needed stops working on its own.
- Select Generate.
- Copy the token, or select Download JSON. Ensure your browser is permitted to download files. If downloads are blocked, you may need to allow downloads from the device's address. Keep the file with the integration that will use it. The page tells you to copy the token now, because it will not be shown again.
- Select Done.
The list then shows the name, the role, the start of the token, when it was created, when it expires, and when it was last used. The full token stays in the file you downloaded. A token set to No expiration shows Never in the Expires column. A token named Automation is saved as videon-pat-automation.json.
Warning: Store the downloaded file where the integration can use it, and where it will not be shared. The device cannot show the full token again. If you lose the file, create a new token and revoke the old one.
We recommend turning on Require sign-in on the same tab before you create tokens, so only an administrator can open this page. Require sign-in for API requests is a separate setting. When it is off, ordinary device requests continue without a token. Administrative requests require a signed-in session or a personal access token. See Setting up password protection.
If the page reports that the token could not be created, contact Videon Support and include a screenshot of the message if possible.
Revoke a token
Revoke a token when the integration no longer needs it. Integrations using that token stop signing in. The Web UI password stays as it is.
- Under Personal access tokens, open the menu on the token's row and select Revoke.
- Select Revoke to confirm. The page tells you that integrations using the token will stop working.
If the page reports that the token could not be revoked, contact Videon Support and include a screenshot of the message if possible.