Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Solved
Browser extension needs 3 clicks to unlock
Hi there,
when I click on my browser extension icon to unlock it, it first shows a window with an field for a password. When I click a second time on the shown window, it changes and shows a buttton to unlock. When I click the button the fingerprint request window opens so I can use my finger print to unlock. Sometimes the ladder pops up without a click.
Why do I need 3 clicks? Why does the finger print request not show up first?
Any ideas
Best,
Stefan
Hi swfischer, thanks for getting back to me!
The behaviour makes sense based on what you’ve described. When integration between the desktop app and browser extension is enabled, Touch ID is handled by the 1Password desktop app, so the browser extension needs the app to be running before it can offer biometric unlock.
If the app isn’t already open, the extension will show the password field while it launches the app and connects to it. Once connected, unlocking with Touch ID will be available instead.
When the app is already running (even if locked), Touch ID is available straight away because the connection is already in place.
If you’d like to keep the two linked but avoid the extra clicks, keeping the 1Password app running in the background should help. You can do that by enabling "Start at login" and "Keep 1Password in the menu bar" in the desktop app under Settings > General.
Alternatively, 1Password for Safari can be configured to use Touch ID without relying on the desktop app. You can read a bit more about this here:Let me know if you have any questions!
5 Replies
Hi, sorry for my late reply.
- I am on an MacBook Pro M1 Max with Safari and Tahoe 26.3.
- It does happen every time (with Safari). There is no change, if I wait a little...
- It only happens if the app is not running. If it is running (but not unlocked) the fingerprint request is immediately.
1P_GemModerator
Hi swfischer, thanks for getting back to me!
The behaviour makes sense based on what you’ve described. When integration between the desktop app and browser extension is enabled, Touch ID is handled by the 1Password desktop app, so the browser extension needs the app to be running before it can offer biometric unlock.
If the app isn’t already open, the extension will show the password field while it launches the app and connects to it. Once connected, unlocking with Touch ID will be available instead.
When the app is already running (even if locked), Touch ID is available straight away because the connection is already in place.
If you’d like to keep the two linked but avoid the extra clicks, keeping the 1Password app running in the background should help. You can do that by enabling "Start at login" and "Keep 1Password in the menu bar" in the desktop app under Settings > General.
Alternatively, 1Password for Safari can be configured to use Touch ID without relying on the desktop app. You can read a bit more about this here:Let me know if you have any questions!
What a great an precise piece of advice. Thanks!
- 1P_Gem
Hi swfischer, welcome to the Community!
From your description, it sounds like there may be a delay in communication between the 1Password extension and the desktop app. When that happens, the extension can briefly show the account password field before biometric unlock becomes available.
Could you answer the questions below for me:
- Which operating system and browser are you using?
- Does this behaviour happen every time you unlock the extension, or more intermittently?
- Is the 1Password desktop app running when you try to unlock the extension, either open or in the background?
I look forward to hearing from you!
