Berry: [Bug] YN0041: Invalid authentication after logging in with `yarn npm login`

[justjake]

• [ ] I'd be willing to implement a fix

Describe the bug

I attempted to publish my package via yarn npm login and yarn npm publish, but yarn failed with an unexpected error

To Reproduce

Using yarn from sources in this repo: https://github.com/justjake/quickjs-emscripten

1. Clone https://github.com/justjake/quickjs-emscripten
2. Try to yarn npm login
3. Try to yarn npm publish

Screenshots

If applicable, add screenshots to help explain your problem.

Environment if relevant (please complete the following information):

• OS: macOS 10.14.6 (18G103)
• Node version: v10.21.0
• Yarn version: 2.1.1-git.20200720.906e9472

[justjake]

Tried yarn npm login --help:

Tried yarn npm login --publish; did not change the result of yarn npm publish

[arcanis]

That's curious - what do you get with yarn npm whoami? 🤔

[justjake]

@arcanis it returns jitl, as expected

[arcanis]

Hm. Any chance it was a temporary registry issue? I published packages this afternoon and it seemed to work, and the message you reported indicate the registry returned a 401 or 403

[justjake]

@arcanis I looked at my ~/.yarnrn.yml, is this supposed to be https://registry.yarnpkg.com? Or should it be configured for something with www.npmjs.com in the URL.

[justjake]

I just tried again after doing yarn set version from sources, same error

[arcanis]

Yep, both registries are the same (the Yarn endpoint is a cname to npm). I'll try tomorrow to publish your package under a test name to see if I can repro. Are you using OTP?

[justjake]

No, I am not.

After running yarn npm logout, attempts to log in now fail as so:

I believe this is because this is the state of ~/.yarnrc.yml after yarn npm logout

[justjake]

What does the --publish flag mean for yarn npm login?

[justjake]

created issue https://github.com/yarnpkg/berry/issues/1663 to track the yarn npm login; yarn npm login bug

[inomdzhon]

I have same issue =(

yarn npm login successfully logged in, but yarn npm publish is Invalid authentication (as undefined)

Here my .yarnrc.yml

nodeLinker: node-modules

plugins:
  - path: .yarn/plugins/@yarnpkg/plugin-workspace-tools.cjs
    spec: "@yarnpkg/plugin-workspace-tools"
  - path: .yarn/plugins/@yarnpkg/plugin-version.cjs
    spec: "@yarnpkg/plugin-version"

yarnPath: .yarn/releases/yarn-2.2.0.cjs

npmRegistryServer: "https://jfrog.space307.tech/api/npm/space307-frontend-local/"

npmPublishRegistry: "https://jfrog.space307.tech/api/npm/space307-frontend-local/"

[inomdzhon]

Ohhh, I forgot to bump version of package and tried to publish existed version on npm 🤦‍♂️ 🤦‍♂️ 🤦‍♂️

Issue is closed for me.

@justjake maybe you have same case?

---

Anyway log by yarn is very uninformative – Invalid authentication (as undefined) say me nothing about real issue =(

[arcanis]

Anyway log by yarn is very uninformative – Invalid authentication (as undefined) say me nothing about real issue =(

Yep, @paul-soporan investigated a bit and it seems that any 403 (which is what the server answers) are reported as Invalid authentication - plus a missing option in one of the calls that caused the as undefined. We'll fix both issues!

[paul-soporan]

Thanks for the reminder @arcanis! I've almost forgotten about this. Will open a PR later today. 👍

[paul-soporan]

Just opened #1809. You can try it out by doing yarn set version from sources --branch 1809 and report back what the actual error message is. If it's confirmed that the remaining problems aren't on our side, we can close this issue.

[merceyz]

Due to the lack of feedback i'll close this under the assumption that what is actually happening is that you're trying to publish an already existing version, which V2.3 will show better error messages for thanks to https://github.com/yarnpkg/berry/pull/1809

[inomdzhon]

Oh, sorry :(
I forget for check, because I downgraded to yarn v1

I checked fix in my branch with yarn v2 and saw next errors

If I try publish without auth

➤ YN0033: No authentication configured for request
➤ YN0000: Failed with errors in 24s 296ms

If I try publish exist version

➤ YN0035: forbidden
➤ YN0000: Failed with errors in 1s 233ms

Looks good than before 👍