Forum Discussion

Former Member's avatar
Former Member
4 years ago

Unlocking Safari 1Password extension every time?

Every time I launch Safari I have to enter my master password to unlock and use the 1Password extension. The "Automatically lock 1Password" setting is turned off.

Is there a better way?


1Password Version: 6.8.9
Extension Version: 2.3.7
OS Version: macOS 12.5.1
Browser:_ Safari

9 Replies

  • Former Member's avatar
    Former Member

    Hey @Corentin, I reached out to you in https://1password.community/discussion/comment/665999#Comment_665999 to help with the extension issues you've written about. Let's keep the convo in that thread to avoid any confusion. I'm happy to help from there.

  • Former Member's avatar
    Former Member

    I have this same issue on my iPad. I’m running version of Apple OS and verion of 1Password is 8.9.7

  • cortig's avatar
    cortig
    Super Contributor

    I just checked on a Monterey Mac and I had the same issue there. I'm trying to figure out whether there might be something that triggers the issue, but on my Ventura Mac at least I was still actively using it and it locked itself up after only 5 minutes, right under my eyes.

    Corentin

  • Former Member's avatar
    Former Member

    Are you running macOS Ventura 13.0.1?

  • cortig's avatar
    cortig
    Super Contributor

    I wonder why it's different in my case then… And it doesn't look like I'm the only one affected since I found https://1password.community/discussion/135401/how-many-times-do-i-have-to-enter-my-password-for-the-safari-extension that seems to describe something similar.

    Corentin

  • Former Member's avatar
    Former Member

    Interesting. I'm not having that issue. Attached is a screenshot of the Safari and 1Password versions I'm using.

  • cortig's avatar
    cortig
    Super Contributor

    The problem seems to be back with 1Password for Safari 2.4.1 unfortunately :-\

    Corentin

  • Former Member's avatar
    Former Member

    FYI - When I updated to the latest version this problem was solved.