Skip to main content

← Back to parent Epic

MAZENG-FT-55 · Secure CLI onboarding and token lifecycle

Feature intent

Users need a trustworthy path to install the Maze CLI, obtain a CLI credential, configure it, and verify authentication.

Why it matters

Users need a trustworthy path to install the Maze CLI, obtain a CLI credential, configure it, and verify authentication.

Expected outcome

Users can begin CLI work with scoped, revocable credentials and accurate platform guidance.

In scope

  • Verified installation and supported-platform guidance.
  • One-time display of scoped, revocable, expiry-visible CLI credentials.
  • Configuration and harmless authentication verification.
Delivery status
IN_BACKLOG
Owner
RootAtSkic (product lead)
Parent Epic
MAZENG-EP-15
Solution approval
PENDING

Acceptance

Acceptance outcomes

  1. 01

    The guide provides verified installation commands and states supported platforms.

  2. 02

    A CLI token is shown once, scoped for CLI use, revocable, expiry-visible, and never stored in plaintext.

  3. 03

    Users can complete configuration and verify authentication with a harmless command.

Dependencies and risks

Dependencies

None recorded.

Risks

  • Legacy creates a general 30-day JWT and stores the full token in the database.
  • Legacy renders the reusable token in the browser.
  • Current distribution ownership and scoped credential design remain to be defined.

Authoritative Architecture tasks

No authoritative Architecture tasks are linked.

Original source