Safari Extension and Touch ID no longer play together

I'm having the exact same issue.

Some more info:

I rebooted my MacBook Air, no change. I entered in the master password, and then put the screensaver on to make me need to auth with 1P again. Went to a site to login, and clicking the locked 1P widget in the login user name field, the 1P extension modal opened and requested my password. There was no fingerprint icon next to the PW field which would prompt me to touch the keyboard widget.

I tried this in Firefox and that extension recognizes Touch ID. (Yes, I realize this is a separate extension, and that Safari support is built into 1P 8.)

I'm stumped.

Hello @kevbob and @Jason9! 👋

I'm sorry that Touch ID isn't working to unlock 1Password for Safari on your Macs. As a start, can you make sure that you have the latest version of 1Password for Safari installed: 1Password for Safari on the Mac App Store

Next, please try the following steps:

1. Close all open web browsers.
2. Right-click on the 1Password icon at the top of your Mac's screen and then click Quit. Wait until the icon disappears.
3. Double-click on 1Password from your Mac's Application folder.
4. Open your web browser.

Let me know if that fixes the issue. I look forward to hearing from you. 🙂

-Dave

Hi Dave

I followed those steps, and indeed that did it. Thank you. What could have caused it to cease working, any idea?

@kevbob

1Password for Safari relies on the 1Password for Mac desktop app for things like Touch ID. It sounds like the communication between the Safari browser extension and the desktop app broke down which is why you could no longer use Touch ID in Safari. The browser extension in Firefox would have it's own separate connection to the desktop app so it makes sense that Touch ID was still working there. Closing and then reopening both the browser and the desktop app allows for the connection to be reestablished.

I'm happy that Touch ID is working again in Safari on your Mac. 🙂

-Dave

I'm having the exact same issue. Initially it just seemed to be an annoyance. But, now it is asking for me to click almost every time I try to use it. My 1Password says it's up to date for my 2022 MacBook Pro—version 8.9.15.

I have run through what you suggested above (quitting Safari and 1Password and relaunching). I'm getting the exact same behavior—no Touch ID, just asks me to click the 1Password icon.

Any other suggestions of what the issue may be, or how to resolve?

Thanks!

@scottrier

Try the following:

1. Turn off - 1Password > Preferences (Settings) > Browser: Connect with 1Password in the browser
2. Right-click on the browser toolbar icon, selecting Settings (General Tab) and then disable Integrate with 1Password app.
3. Quit the browser completely! A full quit, not a close or minimize to the dock.
4. Quit 1Password. While looking at the main window (locked or unlocked)
   • Press Command and Q 1Password should lock and close.
5. Wait a few seconds and then open 1Password from the Dock or the Applications folder and unlock.
6. Turn On - 1Password > Preferences (Settings) > Browser: Connect with 1Password in the browser
7. Open your browser.
8. Right-click on the browser toolbar icon, selecting Settings (General Tab) and then enable Integrate with 1Password app.

If this doesn't help we may need to get you into email support where we can gather logs. support+forum@1password.com if you need to write in.

Thanks Dave, to be sure- restarting browser and laptop didn't fix it, only updating the 1P for Safari did.

Appreciate your confirmation, @kevbob!

@scottrier, you mentioned your 1Password Mac app was up to date, could you confirm your 1Password browser extension is as well? You can find some additional guidance for this on our website if you're interested: How to keep 1Password up to date in your browser

Let me know what you find and we can troubleshoot further from there. 🙂

Andrew, yesterday I confirmed it was resolved. My followup was in response to Dave mentioning closing and reopening the browser reestablished a connection. I explained, I did do those things already when it was not working and that did not help. The only thing that worked was that my 1P for Safari extension app got an update. I was just curious what might have gone wrong, but it's all conjecture, I realize. Again, this is no longer an issue, I was just providing my additional context to what made it work (when it should probably not have broken at all). That's it- this probably has no real answer, I get that- software glitches are ephemeral.