Skip to content

Conversation

@jhernand
Copy link
Contributor

@jhernand jhernand commented Dec 9, 2025

The device flow is more likely to succeed than the code flow because it doesn't require the CLI and the authorization server to agree on a redirect URI. Additionally, the device flow doesn't require the CLI to bring up an HTTP server to receive the authorization code, which can also fail in certain environments.

Users can still explicitly request the code flow with --oauth-flow=code if desired.

The device flow is more likely to succeed than the code flow because it
doesn't require the CLI and the authorization server to agree on a redirect
URI. Additionally, the device flow doesn't require the CLI to bring up an
HTTP server to receive the authorization code, which can also fail in
certain environments.

Users can still explicitly request the code flow with `--oauth-flow=code`
if desired.

Signed-off-by: Juan Hernandez <[email protected]>
@jhernand jhernand merged commit badebeb into osac-project:main Dec 9, 2025
4 checks passed
@jhernand jhernand deleted the use_device_flow_as_default_oauth_flow branch December 9, 2025 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant