Forum Discussion

tempire's avatar
tempire
New Contributor
10 months ago
Solved

Locks incorrectly after passphrase entered during screen sharing session

If I'm signed in through screen sharing to macos, and attempt to use 1password, I get prompted for touchid or to enter a passphrase. I enter the passphrase, and immediately get prompted again, with ...
macos
  • 1P_Dave's avatar
    1P_Dave
    3 months ago

    Hello folks,

    Our development team has released improvements to how auto-lock works with certain configurations such as high-performance screen sharing on macOS. Please update to 1Password for Mac version 8.11.12 or later: 


    If you still see the same issue after updating then please let me know so that we can investigate further.

    -Dave

tempire's avatar
tempire
New Contributor
10 months ago

Indeed - I am using high performance. In standard mode, the problem does not occur.

But also standard mode is effectively just a basic vnc connection which is just awful 😭

1P_Dave's avatar
1P_Dave
Icon for Moderator rankModerator
10 months ago

tempire 

Thank you for confirming that you're using high performance screen sharing. There's currently a known issue where high performance screen sharing will prevent 1Password's auto-lock from working correctly and our developers have a work item open to investigate and fix this issue in a future update. 

Some customer have reported that the following helps them workaround the issue: 

  1. Set the auto-lock timer in 1Password on the remote system to 1 hour: How to set 1Password to lock automatically
  2. Connect to the remote system using standard screen-sharing, instead of high-performance.
  3. Set the auto-lock timer in 1Password on the remote system to Never.
  4. Connect to the remote system using high-performance screen-sharing again.
  5. Set the auto-lock timer in 1Password on the remote system to your preference again.


However, this doesn't fix the issue for everyone and the team is still working to find a proper fix. If the steps listed above don't help then using standard screen sharing is the best workaround that I can suggest at the moment. I'm sorry for the impact that this has on your workflow and hopefully it'll be fix in a future update soon.

-Dave