bitwarden/clients

Unable to login or unlock using 2024.4.0 from npm or Homebrew: `No providers available for this client`

Closed this issue · 3 comments

Problem

I am unable to use the bw CLI since 2024.4.0. Login fails, and an error: No providers available for this client is returned. This is a critical one for me.

Platform

  • macOS 14.4.1 / npm v10.7.0 / node v22.1.0
  • Bitwarden 2024.4.0 installed via NPM
$ bw login
? Email address: my_email@gmail.com
? Master password: [hidden]
No providers available for this client.

Tried uninstall/reinstall, reboot, switching from npm version to Homebrew version (and back). Nothing works.

Researching some other issues here, I noticed some people trying prerelease versions from the build artifacts. So I did the same, and found that e.g. 2024.5.0 from this artifact works (albeit extremely slowly).

Can I please ask that more effort be made to not break the CLI so easily? This has happened too many times before. Just a few:

Seems like some more testing should be done specifically in this area. I hope 2024.5.0 is released asap. 🙏

Adding: Even with 2024.5.0, operations are taking a very, very long time. Example:

$ bw list items
{...redacted...}

real	1m47.212s
user	2m1.794s
sys	0m14.919s

Hi @luckman212,

Thank you for this report. That "No providers available for this client" error message indicates that you have a 2FA method configured which is unsupported by the CLI; Are you using Duo or FIDO2 WebAuthn as 2FA on that individual Bitwarden account? If you are, you can log in using the API credentials or you can consider adding an alternate 2FA method. As a side note, please use CLI 2024.4.0 because that's the current Stable release.

I hope you find this helpful; If you have any questions or concerns, please feel free to get in touch with us via the contact form in the Bitwarden Help Centre. I will now close this GitHub report.

Thank you again,

@SergeantConfused Yes I do use Duo as ONE of my MFA methods. But I also have TOTP and API key. I have been set up like that for years, and was able to log in and use the CLI.

I reverted back to 2024.3.1 and was able to log in.

So I don't think this deserves to be closed instantly.