Proxy Authentication Required error on login

[gamersover]

when setting sync using my github or Microsoft accout, this error is occured

[Info  - 15:16:55.21] Logging in...
[Info  - 15:17:03.563] Exchanging code for token...
[Error  - 15:17:03.678] Proxy Authentication Required

• VSCode Version: 1.51.1
• OS Version: windows10 20H2/ubuntu 20.04

Steps to Reproduce:

1. open sync setting
2. select github or Microsoft

Does this issue occur when all extensions are disabled?: Yes

[cclinuxer]

is there any progroess? I have the same question.

[RMacfarlane]

@chrmarti For extensions, is there anything needed to support proxies, or is it expected that fetch requests would just work?

[chrmarti]

There is support when you end up using the Chromium network stack, but none at the moment if you end up using Node.js' http/s module. Could you point me at the settings sync code doing the request? (Related: #12588)

[RMacfarlane]

Ah, I'm using node fetch. The request is done here:

vscode/extensions/microsoft-authentication/src/AADHelper.ts

Line 571 in c5a8e59

const result = await fetch(endpoint, {

[chrmarti]

That uses http/s from Node and our proxy support added to that currently does not support authentication. Except: If it's basic auth, you could try setting the HTTP Proxy user setting to a http://username:password@proxyhost value.

[TylerLeonhardt]

@chrmarti could we switch to the network stack that does honor the vscode http proxies?

[chrmarti]

Extension don't have direct access to the Chromium network stack. There is the '_workbench.downloadResource' command to allow for simple GET requests, but no command yet for POST requests.

Ideally we would implement support for proxy auth in our existing proxy support for the Node.js API, but I don't have a timeline for that at the moment. (That would also benefit all other extensions.)

[fromthewoods]

Bump on this. Any plans to add proxy authentication support for the built in settings sync?

[chrmarti]

@fromthewoods Have you tried setting the HTTP Proxy user setting to a http://username:password@proxyhost value?

[fromthewoods]

@chrmarti yes that works, but I'd rather not have to expose my password in env variables. It seems that having this configured also breaks other applications that use this env var. Chocolately for example is confused by this entry.

[Glutnix]

All vscode extensions, including the Microsoft and GitHub Authentication extensions, still suffer from a lack of solution - is there a path forward to making extensions use Chromium's Fetch, which is aware of OS level proxy settings, instead of Node's fetch, which doesn't really honor settings.json proxy settings?

Perhaps @TylerLeonhardt, you in a place to push the team on this, as I guess you might be closest to the telemetry on failed attempts, especially due to proxy problems?

[TylerLeonhardt]

@fromthewoods just to be clear, @chrmarti was recommending setting http.proxy the VS Code setting. Not an environment variable. I don't think that should influence running Chocolatey commands. Unless I'm misunderstanding what you're saying?

[MH-ABE]

I'm coming from #178213. I don't know what my proxy address is so I cannot set http.proxy, and it would be kerberos authenticated anyway: #12588 (comment)
By the way, for me Microsoft account login works for settings sync but not Github?

[chrmarti]

@MH-ABE Maybe join #177139 as that is about certificates.

[antonioacg]

https://marketplace.visualstudio.com/items?itemName=ukoloff.win-ca

[TylerLeonhardt]

/duplicate #12588

[VSCodeTriageBot]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!