Skip to content

Upgrade notes: npm and Yarn password logins of local accounts follow the local realm's client-password setting #811

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.

Sign up for GitHub

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

Merged
schmitch merged 1 commit into from
Nov 2, 2026
Merged

Upgrade notes: npm and Yarn password logins of local accounts follow the local realm's client-password setting #811

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/changes/2.2.0/793.upgrade.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
`yarn npm login` (Yarn 2+) and `npm login --auth-type=legacy` take a local
account's password only while the local realm's **Accept passwords from
clients (HTTP Basic)** is on, as the feeds do. In 2.1 these logins took it
whatever `allow_password_basic` said. The upgrade sets the local realm's
setting from `allow_password_basic`, which was off by default, so on such an
install these logins answer 401 for every local account after the upgrade;
accounts of a credential-forwarding realm sign in as before. Turn the
setting on for the local realm under **Admin → Authentication**, or sign npm
in with the browser (`npm login`) or a token from the web UI.
Loading