I was installing a global package that has keytar@7.7.0 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?
I was installing a global package that has keytar@7.7.0 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-407BUT doing
npm config set proxy/https-proxywith 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?