Why was `gcloud auth login` flag `--no-launch-browser` deprecated?

1,612 views
Skip to first unread message

Max Kukartsev

unread,
Apr 1, 2022, 7:31:42 PM4/1/22
to Google Cloud Developers
Hello Google Cloud Developers,

In February 2022 the --no-launch-browser flag to gcloud auth login was deprecated in favor of --no-browser [1]. This is somewhat of a breaking change since it requires a machine with both gcloud and a browser. Could anyone please clarify what prompted this change? Was there anything wrong with --no-launch-browser?

For login with --no-launch-browser, you need gcloud on one machine and a web browser on another machine. You get an OAuth URL, open it in a browser, and paste the code back into gcloud.

With --no-browser, however, you are given a gcloud command to run on another machine which has a browser. But then that other machine needs both gcloud and a browser, which was not a requirement for --no-launch-browser.

Thank you,
Max

References

Horace (Cloud Platform Support)

unread,
Apr 1, 2022, 8:59:30 PM4/1/22
to Google Cloud Developers
Hello,

Apologies for any inconvenience this might have caused. Google is constantly making ways to make validation more secure. However, kindly take a look and comment at [1] as the same issue has been raised. Kindly comment on the public issue tracker to indicate that you are also affected.


Reply all
Reply to author
Forward
0 new messages