Skip to content

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

Closed
wwarby opened this issue May 5, 2018 · 6 comments

Comments

@wwarby
Copy link

wwarby commented May 5, 2018

Versions

@angular-devkit/architect    0.6.0
@angular-devkit/core         0.6.0
@angular-devkit/schematics   0.6.0
@schematics/angular          0.6.0
@schematics/update           0.6.0
rxjs                         6.1.0
typescript                   2.8.3

Repro steps

Run ng update @angular/cli --registry=http://my-company.local/my-custom-npm-registry/

Observed behavior

Unexpected token T in JSON at position 0
TF400813: Resource not available for anonymous access. Client authentication required.

Desired behavior

ng update runs successfully and updates my project

Mention 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:

  • .npmrc in the current directory
  • .npmrc in my user profile
  • HTTP_PROXY environment file
  • Visual Studio Code settings

npm install works fine from the same directory.

@graham-huck
Copy link

graham-huck commented May 5, 2018

@experiencing the same issue from a similar setup. Running npm install @angular/cli seemed to work, but when running ng update from that point forward I received the same error message.

@graham-huck
Copy link

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.

@tim-white87
Copy link

Also getting this error - we use an internal package feed with token auth as a proxy to get our node_module.s

@joshvito
Copy link

joshvito commented May 8, 2018

^ +1 having the same issue with private npm registry in Microsofts VSTS environment.

@hansl
Copy link
Contributor

hansl commented May 8, 2018

Dupe of #10624

@hansl hansl closed this as completed May 8, 2018
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants