git-ecosystem / git-ecosystem/git-credential-manager
Use a `BROWSER` from the environment for interactive login to support VSCode Remote-SSH development
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9.3k
- Forks
- 2.9k
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 14
Description
Feature description
We are using Visual Studio code on VMs to do our cloud development. Recently we switched from using SSH auth to using OAuth and GCM. This works fine on our local workstations as they have a browser. It doesn't work on gcm because it requires an active Desktop Session (e.g. CanUseEmbeddedWebView|CanUseSystemWebView). az login is able to login using the clients browser because it utilises the script managed by VSCode (and listed in the BROWSER env var) to open a browser and interact with it.
GCM could support a similar mechanism, potentially only on Linux(?), to reach out to Azure.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing GCM's OAuth interactive login path and compare it with the BROWSER-based flow used by az login in VSCode Remote-SSH. Determine where the existing desktop-session requirement is enforced and validate that the completed change can open the browser from BROWSER and reach Azure without an active desktop session.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, linux, vscode
- Domain
- authentication, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100