You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
I was installing a global package that has [email protected] as a dependency, behind a proxy on Windows, with a proxy that uses NTLM with Basic auth fallback. I had http_proxy and https_proxy User environment vars set WITHOUT user name and password (much preferred) but the keytar pre-install failed with:
tunneling socket could not be established, statuscode-407
BUT doing npm config set proxy/https-proxy with username and password embedded solved this problem. Most tools no longer rely on basic auth now, can keytar be updated so that no passwords are needed?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was installing a global package that has [email protected] as a dependency, behind a proxy on Windows, with a proxy that uses NTLM with Basic auth fallback. I had http_proxy and https_proxy User environment vars set WITHOUT user name and password (much preferred) but the keytar pre-install failed with:
tunneling socket could not be established, statuscode-407
BUT doing
npm config set proxy/https-proxy
with username and password embedded solved this problem. Most tools no longer rely on basic auth now, can keytar be updated so that no passwords are needed?The text was updated successfully, but these errors were encountered: