When attempting to utilize an npm package from a private repository hosted in a separate Azure DevOps organization, I encountered the following error during the npm install step:
npm ERR! code E401
npm ERR! Unable to authenticate, need: Bearer authorization_uri=https://login.windows.net/2dfb2f0b-4d21-4268-9559-72926144c918, Basic realm="https://pkgsprodcus1.pkgs.visualstudio.com/", TFS-Federated
The content of my project .npmrc file is as follows:
@{scope}:registry=https://pkgs.dev.azure.com/{ORG}/{PROJECT}/_packaging/{FEED}/npm/registry/
always-auth=true
strict-ssl=false
I have followed the documentation on configuring the PAT token with Packaging Read & Write permissions
Attempts to connect using a service connection proved unsuccessful.
I also tried adding credentials to the project .npmrc file to no avail.
.npmrc file with credentials:
@{scope}:registry=https://pkgs.dev.azure.com/{ORG}/{PROJECT}/_packaging/{FEED}/npm/registry/
always-auth=true
strict-ssl=false
//pkgs.dev.azure.com/{ORG}/{PROJECT}/_packaging/{FEED}/npm/registry/:username=ANYTHING-BUT-EMPTY
//pkgs.dev.azure.com/{ORG}/{PROJECT}/_packaging/{FEED}/npm/registry/:_password=BASE64-ENCODED-PAT
//pkgs.dev.azure.com/{ORG}/{PROJECT}/_packaging/{FEED}/npm/registry/:email={EMAIL}
/pkgs.dev.azure.com/{ORG}/{PROJECT}/_packaging/{FEED}/npm/registry/:always-auth=true
Despite generating the PAT multiple times with different scopes, none have proven successful. (PAT generation takes place from User Settings -> Security in Azure DevOps)
On a positive note, I am able to establish a connection to the feed from my local machine using the vsts-npm-auth package.