Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
Forum Discussion
Solved
Native Password AutoFill Extension macOS
So one of the people in my family subscription for 1P relies heavily on iCloud Keychain. The nice piece about using the native autofill extension is entries from both show up together in-line. This happens on iOS (or if you use other password managers it secure by each provider but both are offered the same way together).
in terms of migration and allowing those who wish to use both depending on the context. It would be nice to support the native autofill extension, but further it limits exposure or need for safari extension. Should someone not want to use or can't install the extension due to work policy or just rather not use safari extensions
thanks.
1Password Version: 8.x
Extension Version: Not Provided
OS Version: macOS 12.6
Browser:_ Safari
Hello folks,
The macOS AutoFill feature is now being explored in the nightly version of 1Password! If you're using a nightly build, you'll see 1Password appear as an option for macOS AutoFill.
Since nightly builds are early previews of what we're working on, this feature is still a work in progress and isn't documented. You might notice a few rough edges or areas that aren't fully implemented just yet. Our team is actively refining the experience and working through known issues as we move forward.
We're excited about where this is headed and will share more updates, and a full announcement, down the line. In the meantime, if you have questions or spot anything unexpected while using the nightly version, we'd love to hear from you!
-Dave
231 Replies
i am still hoping they will do add it this year....
- 1P_Dave
Moderator
Former Member
Thank you for the feedback, I've passed it along to the team. 🙂
-Dave
ref: PB-43124655
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: SafariI'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
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
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.
- 1P_Dave
Thank you for the feedback, it's been passed along to the team. Regarding the Safari issues that you're running into, I see that my colleague sent you an email 13 days ago asking for some more information and we're waiting on your reply to investigate further.
Safari web apps don't support browser extensions but you can indeed use Universal Autofill to fill your logins there: Use Universal Autofill in apps and browsers on your Mac
-Dave
ref: PB-38245176
ref: NJN-48466-648 ➕1️⃣
This is a big miss, especially now that Passkeys are getting more common, and the 1Password extension in Safari is (still) totally unreliable.
(Re-posting my comment that was https://1password.community/discussion/comment/705053/, for visibility.)
One use case for native macOS AutoFill are the new Safari 17 https://support.apple.com/104996, where no autofill dropdown appears when focussing a login field. I suppose the universal autofill from 1Password might work here, but I never use that and prefer just to click a login field and have the logins appear in a dropdown, like in Safari.
- 1P_Dave
Thank you everyone for the feedback. I know that the team's current focus is on our existing filling options which you can read more about here:
That being said, I've passed along your requests and feedback to the team internally and they'll look into the macOS filling feature for the future. 🙂
-Dave
ref: PB-37763254
ref: PB-37763285
ref: PB-37763316
ref: PB-37763332 +1 on this for me too. It's surprising that 1Password works to be so seamless and effortless but integrating with the operating system's credential APIs wasn't a priority.
+1 on this feature. Consistency within the Apple ecosystem is always preferable.
