Latest Chrome, 1password extension blocking the basic proxy authentication prompt
Since upgrade to latest Chrome v130 (or perhaps was already the case with v129 which I jumped over), when 1Password Chrome extension is enabled, the basic proxy authentication prompt from Chrome is not coming up (the prompt is supposed to be popping up when accessing a site that is on the internet, thus via proxy, via pac configuration).
With 1Password extension disabled, it works as intended. And was working fine with Chrome v128.
1Password Version: none
Extension Version: 8.10.48.25
OS Version: Windows 10
Browser: Chrome v130.0.6723.59
Comments
-
Hello @girtsn! 👋
I'm sorry that the basic authentication prompt isn't appearing in Chrome. This appears to be an inadvertent side-effect of a recent change to how 1Password handles certain events in the browser. Our developers are currently testing a fix in the latest nightly. If you'd like to give that a try you can find the nightly version here: 1Password Nightly – Password Manager - Chrome Web Store
Let me know if you try the nightly and still see the issue. If testing in the nightly version goes well, the fix will be released to the beta and then to the stable version in the future.
-Dave
ref: dev/core/core#33491
0 -
This still doesn't work in 8.10.50.25
0 -
On behalf of Dave, you're welcome @girtsn. Although I can't provide a specific timeline for when the fix will be available in the stable version, I strongly encourage you to keep 1Password updated. This way, you'll receive the fix as soon as it's released. You can check our website for the latest updates:
Thank you for reaching out. The fix has not yet been released in the stable version (currently 8.10.50.25). I recommend monitoring our release notes and ensuring that 1Password in your browser is always updated.
-Evon
0 -
@Evon, your suggestion doesn't make much sense. Just to be clear, we are an enterprise deployment and we are right now stuck on pushing our entire corp to nightly (even though it breaks passkeys) just so our proxy works... and we don't have time to go around watching each of your release notes to figure out when we can move people back to the main branch.
Given that 1password is trying to push heavily into teams / business / enterprise, this kind of breakage for this long is completely unacceptable.
0 -
I'm sorry for the impact to your organization's workflow. I don't recommend that you use the nightly version in a production capacity for an entire organization since it includes experimental features and isn't tested by our QA team. The fix has graduated from the nightly channel and is now in the latest beta version of 1Password in the browser (8.10.52-14):
We’ve fixed an issue where the 1Password browser extension was blocking proxy authentication.
If testing in the beta goes well we hope to include the fix in an update to the stable version as soon as possible. As Evon mentioned, that'll be noted in our release notes and I'll also leave a note for myself to update this thread.
-Dave
0 -
@Dave_1P , I normally wouldn't run it in a production environment either, but since we are a health system, your 1password bug has caused ALL of our proxies that require authentication to stop working (including all of our medical records), and frankly we can't shut down all patient care and wait for the fix, so we were FORCED to use nightly.
0 -
I'm sorry again for the impact that the bug caused to you and your organization. I'm glad that the nightly version was able to provide a workaround. I'll share your feedback with the team so that we can improve how bugs like this are triaged in the future.
The fix is currently in the beta version of 1Password in the browser and I expect that it'll be released to the stable version soon.
-Dave
0 -
I'm sorry that you're seeing the issue again when using the nightly version. I'd like to ask you to create a diagnostics report from 1Password in your browser:
Sending Diagnostics Reports (browser extension)
Attach the diagnostics to an email message addressed to
support+forum@1password.com.With your email please include:
- A link to this thread:
https://1password.community/discussion/148815/latest-chrome-1password-extension-blocking-the-basic-proxy-authentication-prompt#latest - Your forum username:
girtsn
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!
-Dave
ref: dev/core/core#33491
0 - A link to this thread:
-
Where are we on this? Seriously, it takes a month to fix an enterprise issue?
0 -
A fix for the issue was included in an update to the stable version (8.10.52) on November 12th, however the team has received a few reports that this didn't completely fix the issue. If you're running 8.10.52 or later and still seeing the issue then I'd like to ask you to create a diagnostics report from 1Password in your browser so that we can take a closer look:
Sending Diagnostics Reports (browser extension)
Attach the diagnostics to an email message addressed to
support+forum@1password.com.With your email please include:
- A link to this thread:
https://1password.community/discussion/comment/721695/#Comment_721695 - Your forum username:
JackPo
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!
-Dave
0 - A link to this thread:
-
In the other thread I made with your support colleagues, I realized that likely the issue comes when 1password extension has not been fully initialized yet (clicking the extension icon does not come up with vault unlock prompt). During this time, the proxy authentication popups are blocked.
Your colleague said this conclusion has been forwarded to the team, but its helpful to put it here as well as it provides a workaround (to wait for initialization and then do proxy authentication).0
