docs: document v2 CLI login flow and set-login-method#288
Open
mintlify[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
GKestenberg
approved these changes
May 28, 2026
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
Documents the new v2 CLI login flow that authenticates
portercommands with short-lived session tokens issued through Porter SSO, alongside the existing long-lived token flow.Changes
porter auth loginexplaining the difference betweenv1(long-lived token, default) andv2(short-lived session token) and when to use each.porter config set-login-methodcommand, including thev1/v2options and guidance for selecting between developer and CI/CD environments.Context
The triggering PR adds backend support for a new CLI login flow: the CLI can now authenticate API requests with short-lived session tokens (refreshed automatically) instead of the existing long-lived Porter token. Users opt in per machine via
porter config set-login-method v2and then runporter auth loginto sign in through SSO. Thev1flow remains the default and is unchanged.