I have Azure feed with npm packages to which I’m connecting using Personal Access Token with Packaging read & write scope. Until recently, everything worked fine, but recently when trying to download packages I get an error:
npm ERR! code E403
npm ERR! 403 403 Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature. – GET https://pyvvsblobprodsu6weus63.blob.core.windows.net/…&rscd=attachment%3B%20filename%3D%22worker-farm-1.7.0.tgz%22
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy, or
npm ERR! 403 on a server you do not have access to.
The token is valid. The download takes place via a proxy but it has been verified that the requests are not blocked. Do you have any ideas what could be causing this problem?
2
Answers
Thank you for your answer, but I already use PAT token. Currently, I don't publish any of my packages, I just use Azure Feed to download dependencies to build the project.
Even I received the same error code as yours when, I tried to publish the package with same name and tried downloading it.
In order to resolve this error and to download the existing packages from your feed refer the steps below:-
My
.npmrc file
:-Use the command below to regenerate the credentials for your package:-
Then I tried publishing one new package and download one existing package from my feed and both of them were downloaded successfully
Output:-
My package.json after npm install of both the packages from the feed:-
If you are using other machine, Refer the steps in this section with the use of
PAT token
with Read & write access on Package:-