CLI authentication failed or expired

Reconnect a signed-out CLI and confirm which identity is active.

Why it happens

An interactive CLI login may stop working after its device token expires or is revoked. A pipeline using a service token has a separate set of checks for token errors.

What to do

Start a fresh login from your terminal. Complete the approval in the browser using the account that has access to the project.

Reconnect the CLIShell
apivault login

If the browser approval is what failed, start a new login after signing in to the right browser account. See CLI login for the approval steps.

Check the result

Confirm the active identityShell
apivault whoami

Check that the identity is the one you expected, then rerun the original command. If the identity is correct and the command still fails, check the linked project and its permissions.

Still stuck? Contact support with the error and the steps you tried. Remove secret values before sending.