Skip to content
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

Unable to authenticate, your authentication token seems to be invalid. #50

Open
johnnyreilly opened this issue Oct 29, 2024 · 2 comments

Comments

@johnnyreilly
Copy link

johnnyreilly commented Oct 29, 2024

Describe the bug

When trying to use this project with private feeds I receive this error:

Unable to authenticate, your authentication token seems to be invalid.

To Reproduce
Steps to reproduce the behavior:

  1. Run npx --yes ado-npm-auth in a folder with an .npmrc that looks something like this:
registry=https://pkgs.dev.azure.com/johnnyreilly/_packaging/npmrc-script-organization/npm/registry/ 
                        
always-auth=true
  1. See something like this:
npm error code E401
npm error Unable to authenticate, your authentication token seems to be invalid.
npm error To correct this please try logging in again with:
npm error   npm login

Logs look something like this:

0 verbose cli /usr/local/bin/node /usr/local/lib/node_modules/npm/bin/npm-cli.js
1 info using [email protected]
2 info using [email protected]
3 silly config load:file:/usr/local/lib/node_modules/npm/npmrc
4 silly config load:file:/Users/john.reilly/code/dev.azure.com/URLHERE/.npmrc
5 silly config load:file:/Users/john.reilly/.npmrc
6 silly config load:file:/usr/local/etc/npmrc
7 verbose title npm exec ado-npm-auth
8 verbose argv "exec" "--yes" "--" "ado-npm-auth"
9 verbose logfile logs-max:10 dir:/Users/john.reilly/.npm/_logs/2024-10-29T20_30_18_626Z-
10 verbose logfile /Users/john.reilly/.npm/_logs/2024-10-29T20_30_18_626Z-debug-0.log
11 silly logfile start cleaning logs, removing 1 files
12 silly logfile done cleaning log files
13 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368
14 http fetch GET 401 https://pkgs.dev.azure.com/ORG/_packaging/FEED/npm/registry/ado-npm-auth 284ms (cache skip)
15 verbose stack HttpErrorAuthUnknown: Unable to authenticate, need: Bearer authorization_uri=https://login.windows.net/***, Basic realm="https://pkgsprodsu3weu.app.pkgs.visualstudio.com/", TFS-Federated
15 verbose stack     at /usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:80:17
15 verbose stack     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
15 verbose stack     at async RegistryFetcher.packument (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/registry.js:90:19)
15 verbose stack     at async RegistryFetcher.manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/registry.js:128:23)
15 verbose stack     at async getManifest (/usr/local/lib/node_modules/npm/node_modules/libnpmexec/lib/index.js:27:22)
15 verbose stack     at async missingFromTree (/usr/local/lib/node_modules/npm/node_modules/libnpmexec/lib/index.js:60:22)
15 verbose stack     at async /usr/local/lib/node_modules/npm/node_modules/libnpmexec/lib/index.js:182:32
15 verbose stack     at async Promise.all (index 0)
15 verbose stack     at async exec (/usr/local/lib/node_modules/npm/node_modules/libnpmexec/lib/index.js:180:3)
15 verbose stack     at async Npm.exec (/usr/local/lib/node_modules/npm/lib/npm.js:207:9)
16 verbose statusCode 401
17 verbose pkgid ado-npm-auth@*
18 error code E401
19 error Unable to authenticate, your authentication token seems to be invalid.
20 error To correct this please try logging in again with:
20 error   npm login

Expected behavior
I was expecting no error.

Screenshots
N/A

Desktop (please complete the following information):

Other info

I'm authenticated with Azure DevOps already. Doing npm login doesn't seem to work.

@johnnyreilly
Copy link
Author

johnnyreilly commented Nov 9, 2024

I couldn't get past this and ended up spinning up my own project to resolve this. If you bump on the same issues as me then you might find it helpful too! You can find it here:

https://github.com/johnnyreilly/azdo-npm-auth

and there's an intro blog post here: https://johnnyreilly.com/introducing-azdo-npm-auth

@johnnyreilly
Copy link
Author

As an aside, I was able to get past the initial issue by using npm_config_registry=https://registry.npmjs.org npx ado-npm-auth.

Alas I encountered other issues which I thought I'd share here:

npm_config_registry=https://registry.npmjs.org npx ado-npm-auth
Need to install the following packages:
[email protected]
Ok to proceed? (y) y

🔑 Authenticating to package feed...
Encountered error while performing auth Error: Failed to get Ado Pat from npx AzureAuth: TF909091: Guest users are not permitted to access this organization as per organization policy. For more information, please contact your organization administrator.
An unexpected error ocurred. Re-run with --verbosity=debug for more info.

    at gC (/Users/john.reilly/.npm/_npx/db64d855fa186e0a/node_modules/ado-npm-auth/dist/ado-npm-auth.cjs:157:1982)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async yC (/Users/john.reilly/.npm/_npx/db64d855fa186e0a/node_modules/ado-npm-auth/dist/ado-npm-auth.cjs:157:2113)
    at async bx (/Users/john.reilly/.npm/_npx/db64d855fa186e0a/node_modules/ado-npm-auth/dist/ado-npm-auth.cjs:188:2472)
❌ Authentication to package feed failed.

For now at least azdo-npm-auth does solve this problem. Not sure if there's scope for combining?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant