-
Notifications
You must be signed in to change notification settings - Fork 12k
ng update - "Client authentication required" behind authenticated corporate proxy #10660
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@experiencing the same issue from a similar setup. Running |
I was able to get around this issue by temporarily removing my .npmrc file and removing any references to any non-npmjs npm packages in package.json. |
Also getting this error - we use an internal package feed with token auth as a proxy to get our node_module.s |
^ +1 having the same issue with private npm registry in Microsofts VSTS environment. |
Dupe of #10624 |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Versions
Repro steps
Run
ng update @angular/cli --registry=http://my-company.local/my-custom-npm-registry/
Observed behavior
Desired behavior
ng update
runs successfully and updates my projectMention any other details that might be useful (optional)
I am behind a corporate proxy which requires authentication. It looks like the proxy is being used for my request, but I can't work out from where it is picking up the notion that it should use a proxy to access my custom NPM registry on my local network. It is definitely not getting the proxy address from:
npm install
works fine from the same directory.The text was updated successfully, but these errors were encountered: