Why is 2FA so frustrating in 1PW 8/ Family Membership?

@1P_PeterG Former Member
After lots of testing, I have discovered the root cause. 1Password.com does not save 2FA authentication as cookies. It saves them as localStorage files (or indexedDB). I wish the documentation was clear about this as the Chrome extension "Cookie Bro" wipes these files on every startup. There's a setting that controls it which will solve my problem, but now I have to compromise my privacy to get 1PW.com to work properly. :(

EDIT: Guess they did mention here it but it says "Local Storage", instead of "Localstorage" which changes the meaning entirely.
https://support.1password.com/1password-browser-security/

I've asked the dev of CookieBro if there's any way he can get a whitelisting system for local storage working for this.

Well, I don't want to sound rude, but if you break your system, you own the pieces. Such tools and such means are huge time wasters with questionable usefulness.

If you're afraid of cookies and local storage, use the incognito window of modern browsers. They trash all this data after you close them without plugin.
If you need 1Password in incognito mode, you can enable it to run even in incognito mode in the Chrome extension settings.

Hi @mia, sorry for the complications and frustrations around this. On the other hand, it's great that you found the root of the issue!

It is necessary for 1Password to have some kind of local storage (in the general sense) in order for things to work properly. However, I do appreciate your point about localstorage, and why it would be helpful to document that so that folks who encounter similar situations to this one can figure out what's going askew. I'll put in a request on your behalf!