Help us test the new 1Password browser extension integration in Chrome (1Password 6.5 beta builds)

Options
MikeT
MikeT
edited April 2017 in Mac

Hi guys,

We have a brand new 1Password extension integration for Chrome that we'd love you to test in the 1Password 6.5 for Windows beta builds. We're now moving away from using the WebSocket protocol (localhost/127.0.0.1) and using the Native Messaging protocol instead, which enables the 1Password extension to communicate directly to 1Password. This should enable a faster communication stack and almost no interference by any network-related tools including anti-malware solutions, firewall, VPN, proxies, and so on.

To start testing, please do the following:

  1. Switch over to our 1Password browser extension beta builds here. 1Password browser extension 4.6.4 Beta 3 supports Native Messaging. Chrome may prompt to ask you to permit additional permissions for 1Password extension; this is required because the extension will be connecting to an external process.
  2. Close Chrome before proceeding to install the 1Password 6.5 beta build.
  3. Install the latest 1Password 6.5 beta build. If you haven't signed up for the beta builds, please read this.
  4. Once 1Password 6.5 beta is installed, open it and go to Settings on top right (gear icon) and select Options.
  5. In Advanced tab, scroll down to the 1Password Browser Extension Integration, make sure Enable Native Messaging for Chrome is checked.

FAQ and beta notes

  • If you've authorized the extension, it is normal to see another authorization dialog opens up when you update to the latest beta versions of 1Password extension and 1Password app.
  • Vivaldi and Opera are supported as well.
  • You may notice a few extra processes running in your Task Manager when using Native Messaging; 1Password extension connects to our Native Messaging Host process (1Password.NativeMessagingHost.exe), so you will see a copy for each browser you're using.
  • Be sure to test disabling the WebSocket support and see if 1Password still works in Chrome. WebSocket is still required for Firefox.
  • Support for Firefox is coming later this year.
This discussion has been closed.