Have to enter master PW every time after Mac wakes from sleep
Regarding the 1Password for Safari extension, I seem to have to enter the master password too frequently. I found that if I put the Mac to sleep and then wake it up, the next time I try to log in to a site with Safari, I get the Loading... screen for about 4-5 seconds then it prompts for my master vault password. I have the setting "Lock on sleep, screensaver or switching users" un-checked, so it is not obeying this setting.
See my settings below.
Note that when I open the 1Password app, it comes up unlocked without a password prompt. The problem is only when trying to use the extension to log into a website.
1Password Version: 1Password for Mac 8.10.46 (81046029)
Extension Version: 8.10.46.11
OS Version: macOS 15.1 Beta (24B5035e)
Browser: Safari
Comments
-
The workaround for this is to use Universal Autofill, that is cmd-\ to fill logins. This works on almost every site, and does not require the 1Password password to be entered. However, it would be nice to fix so that the other options for autofill could be used conveniently.
0 -
Hello @mirv! 👋
I'm sorry that you're being prompted to enter your account password more often than expected. It sounds like the communication between the desktop app and the Safari extension isn't working. Try this:
- Open and unlock the 1Password for Mac desktop app.
- Click on 1Password next to the in the menu bar.
- Click Settings.
- Click Browser.
- Make sure that "Connect with 1Password in the browser" is on.
Then in the browser:
- Open your browser.
- Right-click on the 1Password icon in your browser's toolbar and click Settings.
- Make sure that "Integrate this extension with the 1Password desktop app" is on.
If that still doesn't work then do you see a green dot in the browser settings page? Or a different coloured dot and an error message? And if you click on About in the browser settings page what version of 1Password for Safari do you see listed?
-Dave
0 -
Aha, your step 5 fixed it. That setting (Connect with 1Password in the browser) was off. Not sure how that happened. But so far so good. Thank you.
0