Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
Solved
1Password does not work with Safari profiles
The app is pretty much unusable with Safari if you use profiles. Sometimes it won't unlock, sometimes it will only unlock with the icon in the browser bar, sometimes it will unlock but nothing will f...
Hello folks!
Our developers have released improvements to how 1Password communicates with Safari profiles in the latest versions of 1Password for Safari. Please make sure that you're running the latest versions of both macOS and 1Password for Safari:
If you're still seeing issues with the latest version of 1Password for Safari and macOS then I'd like to ask you to create a new diagnostics report from 1Password in your browser so that the team can identify whether you're running into a known issue and help further:
Send a diagnostics report (browser extension)
Attach the diagnostics to an email message addressed to support@1password.com
With your email please include:- A link to this thread: https://www.1password.community/discussions/1password/1password-does-not-work-with-safari-profiles/92139?topicRepliesSort=postTimeDesc
- Your forum username: username
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!-Dave
Still the same issue here. I have already previously communicated with support (RJH-48459-724) resulting in the same suggestions of trying Workaround 1 or 2, both of which work but severely degrade functionality.
So I would like to reiterate that the current state of the Safari extension is really not acceptable and needs to be fixed. I'd also like to point out that https://1password.community/discussion/comment/708916 the following reason was given by 1P_Dave for not implementing the native MacOS Credential Provider API:
In addition, 1Password in the browser and Universal Autofill are developed by our team and that means that 1Password can directly fix filling issues when they occur, something that wouldn't be possible with macOS AutoFill.
Clearly this hasn't happened and, on the contrary, I would think that the native API would generally be more stable (as evidenced by other third-party apps such as Strongbox that implement this functionality).
Having said all that, I've found the following variant of Workaround 1 which, while still not ideal, has reduced friction for me a little bit: Instead of disabling application integration in all Safari profiles, it seems sufficient to disable it in all but one. That way, I can keep app integration including biometric unlocking in my most used profile.
