Closed mikejr83 closed 9 years ago
Sounds like you need a cntlm
proxy! The best way to get support for NTLM in npm is to bug the request team until they agree to figure it out for all of us. ;) npm doesn't handle details of proxying or tunneling itself.
Until recently we were using a local install of Gitorious on our company's intranet to host tools/modules we were building with node. The consumers of the tools would use npm to install from the git repository.
Life was good. Then everyone decided on one source control system. We went with TFS 2013 because it supports each team's needs. One thing it doesn't do is support git/ssh. No biggie, I thought, we'll just use HTTP.
This causes npm an unhappy situation as well...
I fired up wireshark to get that response:
So our TFS git repo uses windows auth / NTLM. How can I get npm pass through my credentials? I already setup git to use wincred? Is there a value I can set in npmrc for credentials? Is this not supported? Can this be supported? :)