Integrate 1P in the native macOS password manager

Having the 1P desktop app also work for passkeys will make the browser extensions almost unneeded. It will be a great addition even outside this whole issue with the Safari extensions.

Another idea would be to integrate 1P in the native macOS password manager as a password service (similar to how it works on iOS/iPadOS) so that i could be used by any browser that supports the native macOS password manager.

Hello @JohnIT! 👋

Thank you for the feedback! I see that I've previously filed a feature request on your behalf here, and I've passed along your new comments to the team as well.

Are you running into issues with 1Password for Safari on your Mac? Can you tell me a little more about what isn't working?

-Dave

ref: PB-36323853

Hi @1P_Dave

Yes, I am also affected by this issue described in the previous thread from where this was split. It seems that if you are actively using multiple profiles in Safari, 1Password extensions have issues communicating with the main 1P macOS app. And there are multiple scenarios that I found as a workaround:

1. 1Password is locked and I click on the macOS 1P app to unlock. In this situation, the 1P extensions will not unlock and basically lose connection to the main app. I then click on the 1P extension in one of the profiles which will show an error that asks for the extension to reload, after which it will start working but only on the profile I do this operation. The other profile will still have a locked 1P extension

2. 1Password is locked and I click on the 1P extension in one of the profiles. In this situation, the 1P extension in that profile unlocks as well as the main 1P macOS app, but the second profile still has a locked 1P extension.

3. 1Password is locked and I close Safari completely and open it back up. In this situation both profiles have a working 1P extension and everything works just fine until 1Password locks again.

Most of the time, because of the issue described above, I gave up on using the 1P Safari extensions and just keep them "dead", and use Universal Autofill for passwords. But as mentioned by others in the previous thread, this does not work for passkeys and there's no way of using passkeys without functioning extensions.

That's why I mentioned my previous request asking for 1Password to adopt the macOS native password API, which will mean that I can use the app itself for passkeys. This has the added benefit of supporting passkeys in other macOS apps as well, not only for webpages in browsers.

@JohnIT

Thank you for providing details on the issues that you're running into. Our developers believe that they have identified the cause of the issue and are coding a fix that should improve the situation with Safari profiles. I hope that a fix will be released to the beta and then the stable version soon.

For the time being, the best workaround is to turn off app integration:

1. Open Safari.
2. Right-click on the 1Password icon in Safari and click Settings.
3. Turn off "Integrate this extension with the 1Password desktop app."
4. Repeat step 2 and 3 for all Safari profiles.

With app integration turned off you'll need to unlock 1Password in each profile separately and you'll need to use your account password (Touch ID and Apple Watch unlock won't be available). I know that it's not the best workaround but I'm sharing it in case it helps.

-Dave

ref: dev/core/core#28250

Thanks Dave, can we get an update on this? We've been struggling with this issue for quite awhile now and it would be great if it were resolved.