Posts made by nick.mclean_7472

@nick-mclean_7472 I added the anonymous user to the view and download packages task and now it gets a little further.

I followed the instruction on setting up an npm feed. Node-sass 4.11.0 is available to be downloaded, and clicking download in ProGet now downloads the package.

But when I try to use npm to download it, I set these config values,

npm config set always-auth=true
npm config set _auth=<my base64 encoded api:keyvalue>
npm config set registry http://<my repo server>/npm/<my feed name>

Then try the install,

npm install node-sass@4.11.0

The command outputs,

node-sass@4.11.0 install C:\temp\npm\node_modules\node-sass
node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.11.0/win32-x64-64_binding.node
...

This download location isn't accessible to me. The package is hosted by ProGet and should be downloaded from there?!

I have an npm package available in an npm feed, and I can use ProGet to explore the package and download individual content files, but when I try to download the entire package through the ProGet interface I get 401 unauthorised.

// 20200217101251
// http://bss-prd-prs01:8624/npm/npm-all/node-sass/-/node-sass-4.11.0.tgz

{
"error": "Unauthorized",
"reason": "You must log in to perform this action."
}

We're using windows authentication, and a test of my user privileges says I have Feeds_DownloadPackage. I'm also configured as admin.

The ProGet Event Log doesn't log my attempted download. And fiddler just says the response was 401 unauthorised.