docs: document HARNESS_AUTH_TOKEN and TTY authentication#3
Open
krrish-berri-2 wants to merge 1 commit into
Open
docs: document HARNESS_AUTH_TOKEN and TTY authentication#3krrish-berri-2 wants to merge 1 commit into
krrish-berri-2 wants to merge 1 commit into
Conversation
- Add HARNESS_AUTH_TOKEN to the required env vars table in installation.mdx - Add learn/tty-auth.mdx explaining the shared secret, why query-param auth is required (ALB strips Authorization headers on WS upgrades), the token flow from secret → pod env → session API → CLI, bootstrap steps, and rotation procedure - Wire the new page into the Learn nav group in docs.json Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
HARNESS_AUTH_TOKENto the required env vars table ininstallation.mdxlearn/tty-auth.mdxcovering: why it exists (ALB stripsAuthorizationon WS upgrades), the full token flow (secret → pod env → session API → CLI), bootstrap for existing clusters, and rotation proceduredocs.jsonContext
HARNESS_AUTH_TOKENwas undocumented. Operators setting up a fresh cluster had no way to know it was required — result was all TTY connections returning 401 with no actionable error.🤖 Generated with Claude Code