Add headless OAuth flow for CLI/automation#2
Open
satyaog wants to merge 1 commit intomila-iqia:mainfrom
Open
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
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.
Add headless OAuth flow for CLI/automation
Supports obtaining refresh tokens without an interactive browser in the same process. When
?headless=trueis used:/loginreturns JSON withlogin_urlandtoken_urlinstead of redirecting. A client can openlogin_urlin a browser for the user to sign in, then calltoken_urlto receive the refresh token./tokencan wait (via an asyncio event) until the browser leg completes, then return the same refresh token to the headless caller.Headless sessions are identified by a JWT in the
headless_sessionquery parameter (signed with the server secret, 5‑minute expiry). An LRU-cached store keyed by that session coordinates the waiting request and the browser callback. Query params are preserved when redirecting to login (e.g.offline_token,redirect=token).