Describe the Bug

Changes to CLI authentication? (Additional authentication required)

Steps To Reproduce

We've been using the Bitwarden CLI for some time now to manage our server secrets (using envwarden, which I created). Today we're suddenly seeing some strange behaviour when using bw login

user@server:~# bw login
? Email address: [email protected]
? Master password: [hidden]
? Additional authentication required.
API key client_secret:

We use an organization account, and we're a paying customer on the hosted version of Bitwarden.

Also having trouble using the --apikey option.

# bw login --apikey
? client_id:  ************
? client_secret: **************
{"response":{"error":"invalid_client"},"captchaRequired":false,"statusCode":400}

Expected Result

Same as yesterday and the last few years? it should work if authentication is successful, be it using email/password, apikey or otherwise. Our password is super long and complex, so even stronger than any client_secret already.

Actual Result

See above

Screenshots or Videos

Environment

• Operating system: Ubuntu 20.04
• Shell: bash
• Build Version (run bw --version): 1.18.1

Additional Context