I love the new Bitwarden 2FA app that was just released. The only issue is the lack of cloud backup. Bitwarden should keep the option of a fully offline mode, where you can backup by manually exporting. But they should also implement the option to add an end-to-end encrypted iCloud integration like the 2FAS app or Raivo 2FA app on iOS.
So that it syncs automatically and the user doesn’t need to worry about manually backing up the 2FA codes themselves.
This is a bit misleading. Yes, mobile devices will back the app up via cloud backups but the 2FA codes themselves are not backed up via iCloud. I’ve just found this out the hard way after getting a new phone and realising the 2FA code for Bitwarden was stored in the Bitwarden app, which doesn’t back up to iCloud. It meant I had to completely delete and restore my account. I’ve switched over to 2FA Authenticator for this very reason. Can you let us know when you implement true iCloud backups, please?
Hi, I’m using iphone and is there a plan to backup the 2FA codes in other way but not iCloud, because I already store my password in it, I’d like to diversify risk, not putting password and 2FA together…
I mean automatically, seemlessly , background cloud sync. No need for user to do anything after the initial configuration. It is just like google authenticator syncing all the 2Fa codes in the google account for user.
I use this topic, which is close enough, because I don’t really understand what’s planned for backups.
Will an encrypted JSON be available in the future ?
On this page, it’s written that you can use different logins for Authenticator and Password manager, but I can’t create any login for Authenticator. Am I reading wrong ? Or is this just a feature not released yet ?
new to the Bitwarden Authenticator I realized today that backup is ONLY possible to a Google account. Since I use a Google-free phone (Samsung 10 with /e/OS as operationg system) I can’t do backups. Please notice that Google-free mobile phones are still a niche but the number of phones running without Google are still growing.
Since backups are crucial (to me) I ask you to implement a backup feature that relies on your Bitwarden cloud not Google (as I don’t trust Google in ANY way). Thank you for your understanding.
Sidenote: I merged now two other threads into this one, as they all requested the same. Therefore I reframed the title here, as currently, the available backup option for the authenticator app is “bound” to the device’s backup system (i.e. “protected with phone backup”, as stated in the corresponding blog article), which is either iCloud or Google One.
So all three threads requested more backup options and therefore also independent one’s from the “phone backup method”.
Hm, Bitwarden does not have a dedicated “cloud storage function”, so I don’t see a “Bitwarden-cloud (!) backup function” independent of the coming sync feature, to be honest… (but if that indeed was your suggestion, then please make a new separate request for that) – And to use “other (non-Bitwarden) cloud options” would now be this feature request…
Speaking of the sync feature: the authenticator app will get a “sync function” with one’s Bitwarden vault (optional!). If that’s what you mean, then you only have to wait…
Thank you for supplying the roadmap. The new Authenticator looks promising! Any chance there is an ETA for Phase 2 with “Authenticator codes synced with Bitwarden account (and within Bitwarden vault)”? This is exactly what I’m looking for.
I’m a part of the latest Great LastPass Flight (since they really screwed up their browser extension earlier this month, even if they did fix it weeks later) and would love to see you guys integrate all of the goodness that LP has without all of the terrible things that started cropping up after they were purchased. Amusingly (to me), I cannot even access their support anymore because I get an infinite login loop on their support site (across all browsers and devices from which I’ve attempted it).
I’m still in the early stages of moving to Bitwarden. And although I haven’t done so yet, I plan to subscribe to a premium plan (mostly to support a good cause).
My understanding is that the premium plan already allows for syncing 2FA keys (using an integrated authenticor) with the subscriber’s vault. Is my understanding correct?
In my case, even after subscribing to the premium account, I’ll probably still prefer to store my keys separately from my passwords. And as such, once subscribed to the premium plan, I would likely use the standalone authenticator rather than the integrated authenticator.
SUGGESTION: In anticipation of the sync feature being rolled out for the standalone authenticator, I hope that Bitwarden will consider allowing each premium subscriber to have access to second vault, the second vault having separate login credentials and being a “keys only” vault to which only a standalone authenticator can be synced.
Sure, I could probably maintain a premium subscription for storing my passwords and separate “free” account just for syncing my 2FA keys. But I’d prefer that the premium subscription officially provide optional access to two vaults, as described above.
I’ll just add that I’m not suggesting that users should be prohibited from syncing passwords and 2FA keys to the same vault. Rather, use of the second vault would be optional.
If you mean by “already allows for syncing 2FA keys (using an integrated authenticator)” that you can use the TOTP codes on all Bitwarden apps where you are logged in with your BW account, then of course – the TOTP codes sync just like everything else in your vault with all BW apps you use.
You can do that just as you want to. And then, you shouldn’t store the authenticator keys (TOTP seed codes) in the integrated authenticator.
As you wrote yourself, it is already not forbidden, to have two Bitwarden accounts (if one account is “paid” – you are only allowed, to have one free BW account – but you already need a premium account for the TOTP functions…).
But I’m not sure, what exactly you’re suggesting. Such a “second account” with separate login credentials would be another BW account as it sounds to me, which already “exists” (unless you suggest an implementation with one account but two different sets of login credentials?!)… And BTW, this should be a separate feature request, and not further discussed in this feature request about more cloud backup options for the dedicated authenticator app. So my suggestion would be: open a feature request about that, and it can be further discussed there. (PS: And maybe search first, if there already is a similar existing feature request…)