Skip to main content

signadot auth

Use signadot auth subcommands to authenticate the CLI.

For a broader overview of API keys --- how to create them, who can create them, and what they are used for --- see API Keys.

Commands​

signadot auth login​

Authenticates the CLI. By default this launches a browser-based device authorization flow. You can also authenticate non-interactively with an API key:

# Browser-based login (interactive)
signadot auth login

# API key login (non-interactive, useful for CI/CD)
signadot auth login --with-api-key <api-key>

Credentials are stored locally at $HOME/.signadot and persist across CLI invocations.

signadot auth status​

Displays the current authentication status, including the authenticated organization and user.

signadot auth status

signadot auth token​

Signadot auth token will print out an authentication token which can be used to authenticate with the API.

TOKEN=signadot auth token
curl -H "Authorization: Bearer $(TOKEN)" https://api.signadot.com/api/v2/orgs/example/sandboxes

Alternative: Environment Variables​

You can also authenticate the CLI by setting environment variables, which take precedence over stored credentials. This is the most common method in CI/CD pipelines:

export SIGNADOT_ORG=<your-org>
export SIGNADOT_API_KEY=<your-api-key>

Deprecated: Config File​

Prior to CLI v0.9.1, authentication was configured via $HOME/.signadot/config.yaml. This method is deprecated in favor of the commands above. See the CLI installation guide for details.