New Device Login Protection is now live for enhanced security protection

Did you not understand the response you received from @Nail1684 above? You can already do this, by logging in to the Web Vault, and going to Settings > My Account > Danger Zone, then clicking Turn off new device login protection.

1 Like

now I only see a rotating loader - these are clearly temporary server problems, although I entered the database through the browser extension. I can’t even go out. Hopefully it’s temporary.

If you tried to follow @grb’s detailed instructions, then you need to login to the web vault, as he wrote.

OK, I disabled the “definition of a new device” in my account.
Now the Application asks for a password every time the browser loads?
Was this how you thought about it? Where is the old version - login password, without codes in the mail?

This was always the case for the Web Vault app.

Try the browser extension, the Desktop app, or the mobile app.

How do I turn off the new email confirmation feature? I am a paying customer and I am willing to pay an extra $200 a year to not have this feature, I hate it, it doesn’t work for me, please allow me to turn it off, I’m willing to sign a legal release, anything, if I can’t turn this off I will have to switch Password Managers.

Thank you,

This is incredibly frustrating.

1 Like

Instructions are here:

DM me… :wink:

Preferably by turning on any form of 2FA. :wink:

:astonished_face:

:laughing:

Hopefully, we can all recognize a joke…

1 Like

What is “Web Vault app”? I don’t have a separate application. I don’t even sincerely understand its purpose , if it doesn’t see the page address in the browser. Only for sorting logins is useful.
Officially in https://chromewebstore.google.com this is called - “extension”. I’m asking about the browser. The browser does not know the concept of “application”, only “extension”.

@grb, please , don’t tell me - “it’s always been like this”.

Previously, when the disease “safety” was still ubiquitous, I established the “extension” BITWARDEN, I entered the password ONCE, in the Settings – “NEVER” . And I forgot about BITWARDEN.
I do not ask you to link my phone number, send an SMS, PUSH-notification or codes in the mail.
How to return to a happy past?

The web vault is either https://vault.bitwarden.com or https://vault.bitwarden.eu. Its primary purpose is handling administrative tasks and account-level settings.

The browser extensions are indeed the best choice for logging into websites from your desktop because they auto-fill. And yes, you can configure them to never logout, to be unlockable with biometrics, etc.

Similarly, the mobile apps are best when using phones because they too autofill, both inside web browsers and (many) mobile apps. They too can be configured to never logout and for unlock with biometrics.

The web vault is a little different. Although it has the ability to “lock”, it can only remain in a locked (or unlocked) state while the web browser is running. If you close the web browser window, it will logout regardless of the timeout setting.

Your risk acceptance decisions are yours to make. The one thing I would caution is to not forget about your Bitwarden master password. A good way to do this is with an emergency sheet. There are situations where you will need to supply it:

  1. If you get a new phone and want to install Bitwarden on it.
  2. If you (re-) install the extension in your desktop web browser.
  3. If you clear your browser’s cookies.
  4. If you run the extension in incognito mode.
  5. If you lose a device and decide to administratively log your sessions out.
  6. if your device somehow falls out-of-sync with the online vault, one needs to log out and back in to fix it.
  7. If Bitwarden itself comes under attack and decides to administratively log everyone out and force reauthentication.

The official Bitwarden documentation calls it the “Web app”, but conventionally, it is known as the “Web Vault” — so I usually compromise and call it the “Web Vault app”.

Here is a copy of the relevant Bitwarden documentation from 2023. It says:

3. If you close your browser window , you will be logged out of your web vault and your browser extension will timeout.

This behavior has been there much longer than that (probably from the inception of the Web Vault).

In the Bitwarden browser extension, if your Vault Timeout is set to “Never”, you will not be prompted for your master password,* even if the browser restarts.

*In my experience, this is the case. However, according to the documentation, the browser extension is expected to time out immediately (disregarding your Vault Timeout setting of “Never”) if you restart your browser. Perhaps this is the case for certain types of browsers or operating systems. If so, it would be best to ensure that your Vault Timeout Action is set to “Lock” (not “Log Out”), and to set up “Unlock with PIN” with the option “Require master password on browser reststart” disabled (you can set the pin to something trivial, like 0).

Yeah, sometimes they even come in the form of just one smiley… :wink:

Just to be sure: if you disabled the new device login protection in the web vault, the corresponding button should then turn blue and it should look like this there (Settings → “My account”-section):

You can correct that community translation by participating yourself: https://crowdin.com (and see here: Localization | Bitwarden)

Yeah, my arrow points to the setting for the option to turn on or off the “new device verification”.

When that button is blue and shows “Turn on new device login protection”, then the new device verification is turned off,

And when that button is red and shows “Turn off new device login protection”, then it is turned on.

1 Like

4 posts were split to a new topic: Vault timeout settings not respected + master password input necessary far too often

Hello, Since new device login protection came in I have been prompted for a verification code during the login process for an existing device. The verification code is sent to my email address but the emails from the EU domain do not arrive until some two hours later, by which time the verification code dialog has long expired. Any suggestions as to how to regain access to my account from these devices? I don’t think anything was said about timeouts and latency of email in the user instructions I was given, so this is annoying, given I have done everything I can to remember and protect my master password, as directed here. I can’t easily fix the email latency problem without using an alternative email address, which I assume means a wholly new account?

I still have access on one other device via the chrome Bitwarden extension, but the android app and browser on the android device still require the device authentication via that slow email.

Grateful for help / advice!

If you can log into the web app on an existing device, your best bet is to either:

  1. Turn on 2FA, so you can use it everywhere without the email delay problem.
  2. Change the account email to something where you can receive emails promptly.
  3. Contact customer support.

I assume this means a wholly new account?

You can change the account email via the web app. It’s highly recommended that you export the vault for backup first, as vault corruption is possible with this procedure.

@Mutineer … what @Neuron5569 wrote… and all tests I (and I think others as well) did, seem to indicate that it’s more related to the email(-server) than to Bitwarden – I always got all test emails immediately – but as you still have control about your Bitwarden email address, you could also try to contact customer support, describe your problem, and see if they can help in any way…

Many thanks. To be clear, I can’t log into the web app on my ubuntu desktop, because it regards the device as new, but I can use the Bitwarden Plugin Chrome extension, which has not yet required a device authentication. I have set the timeout on that to never as a precaution and exported the vault in various formats in the meantime. I’m not sure if the Chrome extension supports changing the account email or the 2FA settings and sync.

Re the email delay, looking at the email headers, there is possibly an SPF failure somewhere for bitwarden.eu in the long path of message transfers and retries before it finally reaches my ISP mailbox host?

@Nail1684 I have contacted customer support, who initially replied quickly, but I don’t think they have figured it out yet. They have asked for screenshots of the Android app message ‘An error has occurred. We were unable to process your request. Please try again or contact us.’ (Can’t do that, no permissions)