Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Please consider integrating 1Password as a Credential Provider on macOS.
For my personal life I am using iCloud Keychain to store my passwords and passkeys, for work we use 1Password and I am quite fond of using it. But I do have something I would like to see improved.
Ever since iOS 17 and macOS Sonoma, developers can now integrate with the system as a https://support.apple.com/en-gb/guide/security/sec6319ac7b9/web#:%7E:text=In%20iOS%2C%20iPadOS%2C%20and%20macOS,is%20built%20on%20app%20extensions., what is that? It is a way to provide credentials like passwords, but more importantly, passkeys to the system, the user will then see all the credentials for a given site from all their password managers, it's really handy! The great thing is, you have already implemented this for the iOS app.
See below how the system UI for credentials came up to let me sign in with a passkey from 1Password:
But sadly, macOS does not get this same feature, instead a browser extension is offered, which works fine, but Apple's popup always pops up first, in my experience anyway. During passkey authentication this is an annoyance: the websites request I sign in with a passkey, so the System UI comes up, but does not find any passkey in iCloud Keychain. So I dismiss the popup, after which the website considers it a failed request. So I have to click the button to try again, and then 1Password comes up with the found passkey.
Another effect is on regular passwords, I have two personal Google account and one for work, this is what happens when I want to sign in with a password:
Needles to say, it's a mess. The system UI always comes above 1Password and it is frustrating. Apparently the system UI can be dismissed with the esc key, but most won't know this "hack".
So please, consider at least giving us the option of integrating 1Password on macOS Sonoma as a Credential Provider like you do on iOS 17. I think it will result in much more seamless experience, one without hacks to use one or the other.
PS: I have checked that Make 1Password the default password manager in this browser, Offer to fill and save passwords, and Offer to save and sign in with passkeys are all enabled within the extension.
1Password Version: 1Password for Mac 8.10.27 (81027003)
Extension Version: 2.21.0
OS Version: macOS 14.4 (23E214)
Browser: Safari
19 Replies
I've been asking for this since 1Password 8 was first released. Hopefully the slightly more positive comments by Travis in the Reddit AMA bode well for this to be implemented in the near(ish) future. I understand it wouldn't completely replace the 1Password Safari extension but it would be fantastic to have for those that continue to experience issues with the extension (which are frustrating to say the least) as either a fallback, or a primary method, with the extension acting as a 'fall-back' for the autofilling types that aren't supported by macOS AutoFill. It would also make signing into desktop apps significantly better. I know Universal AutoFill exists, but there are still consistent issues with that.
- 1P_Dave
Moderator
Thank you for the continued feedback! As Travis mentioned in our Reddit AMA, this is something that we're looking into and we appreciate you letting us know where you'd find this functionality useful!
-Dave
Thanks 1P_Dave
I hope you can really stress to Travis and the other folks actually in charge of potentially implementing features like this that this pain point is growing really long in the tooth. I know you guys are all doing your best to create a great experience for everyone - but this is one instance where the degraded user experience has been consistently pointed out to you all for a number of years now with very little movement on it. Simply saying there are to many limitations to macOS Autofill when there are so many ongoing issues with the Safari Extension is just not good enough; although, I am sure it is unintentional, it really does show a lack of respect for the people who pay to use your App on platforms that you once prioritised.I understand there are priorities and as your company has grown it has naturally reassessed these and (sadly) shifted away from being an 'Apple first' company and started to pivot to Enterprise, Developers and Windows as your primary foci. I think we all (unfortunately) accept that but these obvious pain points are really frustrating to end users. I respectfully don't think enough attention has been paid to issues such as these or the litany of Safari extension issues that you and I have discussed over the years.
The Safari extension as the primary method of autofill was great when there was literally no other option but sadly the issues with it have only grown/multiplied as it has grown more complex. I appreciate the reasons for this are not solely on 1Password - I understand that Apple have imperfect APIs and implementation of APIs that are sub-par in areas but this lack of attention to a clear customer pain point would never have lasted this long in the 1Password 6 and 7 days.
I hope as a company you can remember your roots as an Apple first App and service, and whilst we may no longer be your primary target market maybe you can find a way to better respect the community that at one stage 1Password clearly loved. We still have a lot of affection for your App and Service, and really do want it to be the best it can be across all platforms, we're just tired of being the afterthoughts in terms of user experience that we've clearly been for a number of years now.(To state what I hope is obvious - none of this is directed at you specifically as an individual as I know time and time again over the years all you do is respond to us users on the forum here and try to help us in the best way you can. I know we all really do truly appreciate it. I hope this post can be flagged to senior management.)
EDIT: Just in case it wasn't obvious - macOS Autofill just works. When using Apple Passwords, or Strongbox (which I trialed for a while but didn't adopt as local vault and iCloud vault syncing just wasn't what I wanted) I NEVER had an issue where it failed to fill a username or password. I never had an instance where it bugged out or froze. Compare this to the 1Password Safari Extension just today, where I have had at least 4 times where it has failed to fill a username and password.
Your insistence on maintaining control is actively degrading user experience.
We’re a 1Password Business customer, and we’ll be churning over this issue. The current implementation breaks the flow for passkey-based IDPs that use their own WebAuthN credential providers. Our users constantly have to click “bypass”just to access the Apple-provided UI for every other credential source.
This isn’t a technical limitation, it’s a philosophical one. You already implement the Credential Provider API correctly on iOS. There’s no excuse not to do the same on macOS.
Please get over the need to own the entire experience and implement this properly.
- 1P_SimonH
Community Manager
Hi troutzero,
Thanks for taking the time to give this feedback. If you didn't see our latest Ask Me Anything on Reddit, I wanted to link a response to a question about supporting macOS autofill just to share our current thinking:We've been taking a heavier look at MacOS autofill in the second half of this year to see if the limitations we encountered previously have been alleviated or if they're still present. Although not perfect and not where we ideally want it to be, integrating with native MacOS autofill is looking promising. If we're able to have our concerns addressed with the API to ensure 1Password customers can seamlessly use MacOS autofill without fear of falling through the cracks, I don't see a reason to not integrate in the near future.
Whenever I set up a macOS device for a new employee, there are three or four, maybe five, separate sign-ins, all in private webkit windows. This is a hassle.
You'll want to look into Intune's https://learn.microsoft.com/en-us/mem/intune/configuration/platform-sso-macos to fix that problem. It's recently gone GA.
When deploying devices via the Apple Device Enrollment (ADE) route and user-affinity, they sign in once to a Microsoft 365 account at the OOBE to assign the device to them.
Then they enter a macOS username and password at setup assistant. Once on the desktop, the click the prompt to register their device with Platform SSO and sign into their Microsoft 365 account, once that's completed all other Microsoft 365 sign-in screens log them in automatically (in applications using the right authentication libraries), and browsers like Safari, Microsoft Edge and Chrome (all with some pre-reqs).Just wanted to mention that I have been hoping to see this feature being integrated.
We use Microsoft Intune for MDM, which does not integrate well with macOS, especially during device onboarding.
Whenever I set up a macOS device for a new employee, there are three or four, maybe five, separate sign-ins, all in private webkit windows. This is a hassle.Passkeys make this process so much easier. But using 1Password passkeys means having to have a separate device configured, which isn't much of an improvement to be honest. So I stick to physical security keys instead.
As an aside, I cannot for the life of me figure out how to get Microsoft 365 passkeys in 1Password to work. If you have any advice on that, please let me know, because Microsoft is doing something weird, and i can't figure it out.
- 1P_Dave
Thanks again for the feedback, I've shared it with the team. I'm happy that the suggestion to use separate browsers helps. 🙂
-Dave
Hi Dave, thanks for your response.
Yes, macOS AutoFill doesn't over all of the features. But that hasn't stopped you on iOS/iPadOS, there you can choose to use the browser extension and/or AutoFill. Also consider that 1Password AutoFill is not on by default, users have to enable this in settings. So users always have the option to either use the extension or use autofill, they have to pick.
I'm not saying to drop the extension and only go forward with AutoFill on Apple devices, but why not offer the option? Users who know the advantages will enable it and those who want everything 1Password has to offer can install the extension or use Universal AutoFill.
As for the password popup problem, I solved it with the advise you gave to use separate browsers. Chrome for work, Safari for personal. Although if 1Password will ever support macOS AutoFill I would instantly drop Chrome and just use Safari for everything.
- 1P_Dave
Thank you for the feedback, I've merged your other comment into your existing thread so that we can keep the conversation in one place. The native AutoFill feature in macOS doesn't support all of the features that 1Password offers which makes completely replacing our extension with it a non-starter. These features include but are not limited to:
- Filling identity and credit card items.
- SSH key generation.
- Compatibility with integrations like Privacy.com and Fastmail masked email aliases.
- Use of 1Password's own filling brain.
- Support for features like sign-in with, autosubmit, and 1Password's standalone password generator.
- Smart/Memorable password generation right on the page using 1Password's password generator.
Replacing 1Password's browser extension with macOS AutoFill limits what 1Password can do to only the features that Apple decides to add to macOS AutoFill. That being said, I have filed a feature request with our team to look into expanding support for passkey saving and sign in in Safari Web Apps and other desktop apps. The team will consider all options, including macOS AutoFill.
On iOS 17 and aligned releases on their other platforms they introduced a capability where you can pick a username/password from iCloud Keychain in any textfield in cases where the system did not detect it as a username/password field. On the new beta's (iOS 18 and aligned releases) Apple is opening this up so other credential providers, like 1Password, can also fill out credentials in textfields that were not detected as a username/password field.
I'm glad to hear that this is now working with third-party password managers. It's a common point of confusion for folks who have disabled iCloud Keychain for iOS AutoFill but still see it when double-tapping on a field and then tapping on AutoFill.
Apple's popup always pops up first, in my experience anyway. During passkey authentication this is an annoyance: the websites request I sign in with a passkey, so the System UI comes up, but does not find any passkey in iCloud Keychain. So I dismiss the popup, after which the website considers it a failed request. So I have to click the button to try again, and then 1Password comes up with the found passkey.
This sounds like you might have both iCloud Keychain and 1Password enabled in Safari which is causing a conflict. Can you try these steps:
- Make sure that 1Password is set as a default password manager in Safari and that the built-in password manager is turned off: Turn off the built-in password manager in your browser
- Click on the in the menu bar and then clicking System Settings.
- Click Passwords.
- Click Password Options.
- Turn off "AutoFill Passwords and Passkeys".
Then try to sign in with a passkey again: Save and sign in with passkeys in your browser
Let me know how that goes. 🙂
-Dave
ref: PB-40546086
