REMINDER: the community is in read-only mode until July 2nd. This is part of our platform upgrade! Learn more in the FAQs

Forum Discussion

MirekRusin's avatar
MirekRusin
New Contributor
1 month ago

Re: 1password locks within 10 seconds on High Performance or Dynamic resolution screen share on macOS

When accessing macOS through Screen Sharing Auto-lock thinks application is not used and will kick you out after few seconds, you have to re-enter pass – it makes application unusable.

3 Replies

Replies have been turned off for this discussion
  • ernestosanchez's avatar
    ernestosanchez
    New Contributor

    This also is triggered by Jump Desktop.  We require the best quality/performance remote session so this work around doesn't work for us.  However, this workaround is working, so far. The remote use needs to disconnect their session first. Then I remote in via screen sharing or Apple Remote Desktop.

    • Step 1: While connected via standard (non-high-performance) screen sharing, set 1Password auto-lock to 1 hour
    • Step 2: Disconnect, then reconnect using standard mode screen sharing
    • Step 3: Set auto-lock to Never
    • Step 4: Disconnect, then reconnect using high-performance mode

     

    Looking forward to when this bug is actually fixed, everything I find says the latest update fixes this.

    • 1P_Dave's avatar
      1P_Dave
      Icon for Moderator rankModerator

      ernestosanchez​ 

      I'm sorry that the issue is affecting you as well, I'd added your report and comment to the internal work item open for the issue.

      -Dave

  • Trevor_1P's avatar
    Trevor_1P
    Icon for Moderator rankModerator

    Hi MirekRusin​,

    To confirm, when sharing your screen on macOS, are you using the "High Performance" option? If so, there is a known issue that our Development team is currently investigating that can cause the 1Password app to lock prematurely when the High Performance option is selected. 

    As a workaround, other users experiencing the issue have found that toggling the High Performance setting off resolves the issue for them. If this corresponds with the behaviour you're seeing, let me know and I can add your report to our internal tracker for the issue.

    Issue=DV-301