1Password chrome extension keeps locking out every few minutes due to this! — Sometimes there is actually an update available for chrome (I use their canary channel so updates are very frequent), but a few times I've noticed this coming even when Chrome says there aren't any updates. This makes the extension almost unusable for me since it's used not just for passwords, but also used for autofill. Why should 1Password stop working every time chrome has an update? It doesn't make a lot of sense. 1Password Version: 1Password for Mac 8.5.0 Extension Version: version 2.1.4 OS Version: Mac 11.6.1

steph_giles @jamesbull has nailed the issue. Restarting Chrome is an ordeal. As an agency many of our customers are providing Google Accounts for our employees. The easiest way to manage these multiple Google Workspace accounts is to use multiple Chrome profiles. Users will frequently keep Chrome open for 3-4 weeks at a time with 5-6 Chrome profiles with 5-6 windows per profile with 20-30 tabs per window (yes, the machines are beefy and people are using tab suspension) and only restart when an OS Chrome when an OS update is pushed. People even take this a step further by using multiple virtual machines and then facing this problem with multiple instances of Chrome running on virtual machines all on one physical machine... Yes, this is probably not a common use case but you'd be surprised with software devs... Also, it would be almost impossible to measure if people are doing this, it's just going to look like one account being used on many machines... Additionally, people are using 5-6 1Password instances due to being given accounts on client 1Password instances. This experience has gotten way better so props on that 1Password. Still not there yet though... I'd still like to see an experience like Slack Connect for 1Password to make working with external businesses easier but I imagine that'd be amazingly difficult to do with a secure architecture... And it would lead to a significant reduction in paid user accounts for 1Password. Our employees can basically have 6 accounts, one paid for by us and 5 by clients.... It's still painful using multiple 1Password instances though where those instances have unique passwords, I know 1Password will unlock all instances if they share the same master password and that because of the unique architecture of the 1Password Master Password password reuse doesn't have the same negative implications it does elsewhere... That still breaks most users brains though "oh, don't reuse passwords anywhere, it's really bad... Oh except the most important password you have, your 1Password Master Password, it's fine to reuse that... But remember, only as a Master Password on other 1Password instances... The irony (whilst technically sound) of 1Password deploying password reuse to solve a UX problem does not seem to have been lost on the community and was thoroughly discussed here: https://1password.community/discussion/comment/608291/#Comment_608291 Realistically one should close out their browser and update it quickly to be as secure as possible. That's best practice. It's just not always realistic if it needs to be done weekly or daily. The current user experience feels like 1Password is getting opinionated about what people's update habits should be around other apps beyond 1Password. That feels like overreach and and a holier-than-thou attitude. It just leaves a bad taste. I don't think that's actually what's happening here, I think it is a genuine architecture of the browser extension/desktop app relationship but that won't matter to a user who doesn't care to understand the nuances of the architecture. They just see 1Password having opinions about how up to date their browser is and see functionality being restricted in order to force behaviour change and not monthly or quarterly, sometimes weekly or daily depending on how frequently Chrome updates rollout (which is not to their stated fortnightly schedule btw, that's an aspiration, it usually whenever something urgent needs patching). Imagine if Chrome started restricting access to Google Products if the browser was out of date and this happened daily or weekly... Yeah nah. 1Password is a critical tool that gets used hundreds of time per day by our users. Using that power to force people to reboot other applications by restricting access to that tool and doing that multiple times per week (even if unintentionally) feels like negligence at best and abuse of power at worst. This is part of a broader issue for the tech industry (Google is going to face it with Chrome and their 'traffic light's update system in Chrome) which is that users will revolt if core applications start needing full restarts daily or multiple times per day. There is going to need to be a concerted architecture effort by most applications to enable live patching wherever possible and keep the requirements for full restarts to the absolute bare minimum. Applications that manage this engineering challenge will inherit the users of applications that choose to prioritise engineering ease over UX. What I'm saying is that 1Password have made architecture tradeoffs that cause a poor user experience, that's fine but I imagine 1Password is flying close to the sun on this and is getting to the point where they're crossing the line of what they can force users to do... I mean only 1Password have access to user churn data but if I had to guess, this sort of thing would be driving it up. It feels like a Steve Jobs moment is required where he comes in, says that he doesn't like the way the bounce animation works on iPhone scroll and holds the entire iPhone project until the bounce animation feels just right. Yeah it's a good damn engineering pain in the backside but it's what makes for iPhone level UX driven success. If 1Password wants that level of success, keep prioritising the UX. Keep refusing to ship product with a solid engineering solution but a bad UX. Don't ship until the engineering is genius and the UX is best in class. There are plenty of other password managers out there... Don't mess up your USP.

Hey 1Password.. Chrome has moved to weekly updates: https://security.googleblog.com/2023/08/an-update-on-chrome-security-updates.html and I'm at wits end with 1Password failing. I certainly can't try to get my family to start using our teams account when the passwords which were "just there" in their chrome profile don't go missing. I never have cared what security benefit there is from having the extension validate the browser.. now that the browser is pretty much always considered invalid, we really need a better workflow here.

OMYGOODNESS IT'S CHRISTMAS The 1Password browser extension in Chrome will now maintain a connection with the 1Password app even when a Chrome update is pending.

@ObjectConsulting I'm happy to see your enthusiasm for the new update, our development team took everyone's feedback to heart and worked hard to get this right. 💙 -Dave

Can this please be fixed (at least in the short term) by letting us disable code signature validation for selected browsers? We finally have the ability to select trusted browsers, so this really isn't a huge leap. I might try disabling chrome-auto updates because this behavior is so frustrating.

1Password chrome extension keeps getting locked because an update is available

85 Replies

Former Member
3 years ago
Hi @pluhin, I'd like you to send over the following so we can take a closer look at what may be going on:

The extension console log: https://support.1password.com/cs/extension-console-log/

A diagnostics report: https://support.1password.com/diagnostics/

Attach the logs and diagnostics to an email message addressed to mailto:support+forum@1password.com.

With your email please include:
* A link to this thread: https://1password.community/discussion/comment/667544#Comment_667544
* Your forum username: pluhin

You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks!
Former Member
3 years ago
Hey @Joy_1P.
I don't have any pending updates to chrome, 1password extension or 1password desktop application. And it still saying that Chrome has pending updates and I need to restart it. Every time.
Former Member
3 years ago
In my company MacBook, I have a similar problem using 1Password.

Since I'm not an admin user by default, Brave browser is always asking for admin to update (https://github.com/brave/brave-browser/issues/11288) to fix this I moved the Brave browser to my user application folder, in this way it auto updates.

But by doing so, 1Password on Brave browser is always saying: "Brave has an update available. Restart Brave to install the update and reconnect with 1Password."
Former Member
3 years ago
I'm deploying 1P to a small business of about 35 people and this issue is making me rethink the process. My personal 1P account has an easy to remember password. So when Chrome updates 2-3 times a week, no problem. But for the business account I set up a strong password policy. This is not an issue...unless you have to type it in 2-3 times a week. As it stands, every time Chrome updates I'm forced to dig up the emergency kit for the password and the secret key or I'm only able to use my personal account. The only practical solution seems to be to dumb down the security on the business side to something easy to remember, which sort of defeats the purpose. I can only imagine what our users are going to choose as their main password to get around this issue ("password"). I love 1P which is why I chose it for our business but I'm not willing to deal with this potential headache. We may just be better off with the shared Google Sheet we use now.
Former Member
3 years ago
Bumping this. If there isn't a way to validate both the pending and old signature, I'd like a way to disable signature validation.

If someone can replace my chrome binary without me noticing or otherwise inject code, for my purposes, they might as well have access to my 1Password (and I'll probably sign in anyway). I understand this being the default but please make it configurable.
Former Member
3 years ago
Hey @Joy_1P, I think it's connected. So in my case, if there is a waiting update it asks password almost every time. Likewise I have a lot of tabs open, only restart my browser once in a few weeks. Is there a workaround to this?
Former Member
3 years ago
This is very annoying and I think part of the ultimate solution here is the same thing that will help on other platforms: Make the browser extension fully capable on its own.

The annoyance of 1Password locking at every turn is something that happens:
* When Chrome is ready to update
* When using a browser that 1Password doesn't know about like Ghost
* When using a platform that doesn't have a native app, like Chromebooks (ChromeOS)
* When using iOS, though fortunately Touch/Face ID reliably unlocks 1Password

In all of these cases, we could lower the annoyance-factor to zero if the 1Password browser extension was fully capable on its own, able to set the same Security preferences as the Mac app.
Former Member
3 years ago
Hey @kirbiyik, are you asked to enter your Account Password even when there are no updates needed in Chrome? If so, then it might be a totally different issue. Let me know more about what's happening and I will do my best to help.
Former Member
3 years ago
Same, this is super annoying
Former Member
3 years ago
Same here, about to cancel my subscription. I have a rather long master password. Chrome extension makes me enter my pass ~10 times a day. If I cancel integration with desktop app, it asks constantly.

Any solid plans to address this issue?

Forum Discussion

1Password chrome extension keeps getting locked because an update is available

85 Replies

Featured discussions

September at 1Password: Browser versions, enhanced security, and new integrations

Recent discussions

Android 1password face biometrics

QuickFile app not working with 1P

"Sign in with" never kicks in

Auto-Lock totally doesn't work

Autofill not working with Aegis Authenticator