Add passkey browser auth to CLI - #3804
Closed
ntner wants to merge 1 commit into
Closed
Conversation
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
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.
What is the feature/update/fix?
Feature: Passkey Browser Authentication for the CLI
The CLI now completes two-factor console authentication through your browser. When a session token challenge is issued, the CLI opens the console's login page in your default browser, where the WebAuthn ceremony runs with whatever authenticator you use: a passkey (Touch ID, Windows Hello, or a synced passkey) or a USB security key. The signed assertion is returned to the CLI over a short-lived local callback and the command proceeds.
The direct USB security key path remains available behind an environment variable:
CONVOX_WEB_U2F_DISABLEtrue/ unsettrue, skip the browser flow and authenticate directly against a physical USB security key (the previous behavior). Useful on headless machines with no browser.How to use it?
Update your CLI, then use it as usual:
When a command requires the security token challenge, the CLI prints a link and opens your browser automatically. Complete the passkey or security key prompt in the browser, then return to the terminal; the CLI continues on its own. The browser must run on the same machine as the CLI, since the result is returned over a local callback. The browser step times out after 5 minutes.
On a headless machine, or to keep using a USB security key directly, set the variable in the environment of the commands you run:
Does it have a breaking change?
No breaking changes to commands or configuration. The default authentication flow changes from the direct USB key path to the browser flow, which supports USB security keys as well as passkeys. If you prefer the direct USB flow or work without a browser, set
CONVOX_WEB_U2F_DISABLE=trueto keep the previous behavior.Requirements
To use this feature, you must update your CLI to version
20260714094620or newer.convox versionconvox update