Skip to main content
November 16, 2021
Question

v8 passing state from Browser to Desktop Client

  • November 16, 2021
  • 22 replies
  • 397 views
  1. New desktop client installed, v8.4.0 (currently the beta build, but will try with updated version soon)
  2. Open client, fill out all details (for a business site configured with Duo MFA)
  3. Browser opens with Duo Prompt, respond to prompt successfully (push or yubikey, doesn’t matter)
  4. Browser looks like it ‘tries’ to pass the session back to the desktop client but just hangs.
  5. Result is client setup is unsuccessful.

Currently the only way to get around this is to set the Duo profile to bypass, but that isn’t a sustainable workaround. I think it also affects writing from the client to the service.

Version of Windows 10 is 20H2. Edge version is 89.0.774.75. Our installation of Edge is highly managed so it may be a trusted site thing, but I need to know what settings to give it to ensure it can interact with the client successfully.

I do get that this may be a browser issue, but wasn't sure where to start it. This works fine on v7 or on v8 with a personal vault vs. business.


1Password Version: 8.4
Extension Version: 2.1.8
OS Version: Windows 10 20H2

22 replies

1Password Employee
January 7, 2022

Excellent news, @bachirica. Thanks for sharing. :)

Ben

January 11, 2022

Only minor complaint here is that the handoff is a little clunky compared to v7. It opens a browser tab for the duo dialogue and you have to manually close it after it hands it back to the client. That's probably on Duo with their new universal prompt implementation, but kind of a step back. The upside is I can use my security key in that dialog vs. the v7 implementation.