Repository navigation
docs: add service account and personal access token pages - #56
Conversation
Document the two non-interactive ways to authenticate with FloxHub in Flox CLI 1.14.0: service accounts (org-owned, for CI) and personal access tokens (user-owned, for headless machines). - concepts/service-accounts: access levels, creating, issuing tokens, using in CI, revoking, and rotating without downtime - concepts/personal-access-tokens: creating, using via --token-file or FLOX_FLOXHUB_TOKEN, viewing and revoking - tutorials/ci-cd: new section on when a pipeline needs credentials and how to give it its own identity - concepts/floxhub, concepts/organizations: point at the new pages - docs.json: add both to the Concepts nav Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L9FR5u25zs4iMXnS4V7uwm
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L9FR5u25zs4iMXnS4V7uwm
|
Added the The page now explicitly documents support for JWT access tokens, personal access tokens, and service account tokens. Token-file login does not open a browser or prompt for input. JWT access tokens are validated locally; opaque PATs and SATs require FloxHub connectivity for validation. The canonical man-page source change is in flox/flox#4581. Verified a synthetic JWT token file without a reachable FloxHub endpoint, plus PAT and SAT inputs via both a file path and stdin against a local fake FloxHub endpoint. Also confirmed opaque verification fails when FloxHub is unreachable. |
## Proposed Changes Clarify the canonical `flox auth login --token-file` man-page source: - explicitly document support for JWT access tokens, personal access tokens, and service account tokens - explain that token-file login does not open a browser or prompt for input - distinguish locally validated JWT access tokens from opaque PATs and SATs, which require FloxHub connectivity for validation The regenerated Mintlify page is included on top of [flox/docs#56](flox/docs#56). ## Verification - exercised a synthetic JWT token file successfully without a reachable FloxHub endpoint - exercised PAT and SAT token files against a local fake FloxHub `/me` endpoint - exercised `--token-file -` for PATs and SATs - confirmed opaque token verification fails when FloxHub is unreachable - `treefmt` passed in the pre-push hook ## Release Notes N/A — documentation correction only.
Documents the two non-interactive ways to authenticate with FloxHub, both new in Flox CLI 1.14.0.
New pages
concepts/service-accounts(Team/Enterprise) — an identity that belongs to the organization rather than to a person, for CI and other automation. Covers the two access levels, creating an account, issuing and revoking tokens, using one in CI, and rotating without downtime.concepts/personal-access-tokens(all plans) — signs the CLI in as you, for SSH sessions, containers, and other machines without a browser. Covers creating, using via--token-fileorFLOX_FLOXHUB_TOKEN, and revoking.Existing pages
tutorials/ci-cd: new "Authenticating with FloxHub" section — when a pipeline actually needs credentials, and giving it its own identity instead of a person'sconcepts/floxhub: points at both pages from the authentication sectionconcepts/organizations: a Service accounts section above the existing machine access tokensdocs.json: both pages added to the Concepts nav🤖 Generated with Claude Code
https://claude.ai/code/session_01L9FR5u25zs4iMXnS4V7uwm