514 auth

Use 514 auth to establish the trust boundary for the CLI agent harness.

Once authenticated, follow-on commands (orgs, projects, setup, and link) can act on your cloud OLAP workloads with the correct account and project permissions.

Usage

514 auth [OPTIONS] <COMMAND>

Subcommands

Start browser-based sign-in.

514 auth login

Expected outcome:

Browser sign-in flow opens.
CLI receives a valid session.

Recovery:

If browser launch fails, open: https://www.fiveonefour.boreal.cloud/login
Retry command: 514 auth login

Whoami

Show the currently authenticated account.

514 auth whoami

Expected outcome:

Prints account identity and confirms active session.

Recovery:

If unauthenticated, run: 514 auth login

Logout

Clear local auth session for the current machine.

514 auth logout

Expected outcome:

Local session is removed.

Recovery:

To authenticate again, run: 514 auth login

Typical Flow

514 auth login
514 auth whoami

Options

--api-url <API_URL>: Override API base URL (HOSTING_CLI_API_URL).
-o, --org <ORG>: Organization name or ID.
--json: Output as JSON.
-v, --verbose...: Enable verbose output (-v debug, -vv trace).
-h, --help: Print help.

514 auth

Use 514 auth to establish the trust boundary for the CLI agent harness.

Once authenticated, follow-on commands (orgs, projects, setup, and link) can act on your cloud OLAP workloads with the correct account and project permissions.