Native Password AutoFill Extension macOS

lamsquat

Thank you for the feedback, I've filed a feature request on your behalf as well. 🙂

Regarding the last two bullet points in your reply:

1. With a recent update to macOS, Safari now allows browser extensions in web apps. There is an issue where 1Password for Safari won't unlock properly in a Safari web app if app integration is turned on and our developers are aware of the issue. 1Password in the browser already works in web apps from browsers like Chrome even with app integration turned on.
2. Are there any particular apps where Universal Autofill isn't working? Our team can investigate further and get those fixed.

-Dave

ref: PB-44582138

I just want to add my voice to the many poeple here asking about the native OS integration. In the past this was one of the major strengths of 1P, but has been becoming substantially worse since the release of version 8.

That being said my main pain points with this right now are
- Passkey support in native apps such as some enterprise stuff as well as a growing list of consumer apps such as Discord and Home Assistant
- Password dropdown in Safari webapps or other web technology based desktop apps
- Universal autofill does not work on sometimes on apps with bad accessibility support while the native fill does work in almost every 'secure' input field.

I would really appreciate progress in this regard :-)

Greetings

nthnchng

Thank you for the detailed feedback, I've filed your request with our Product team and included your entire comment. 🙂

-Dave

ref: PB-44182228

I would also like to see this!!! Please include my +1 in this feedback request as well.

This would make the macOS user experience better on multiple fronts:

1. More elegant verification code handling - using system dropdowns to show 1Password codes instead of requiring Universal Autofill
2. Simpler setup for 2FA - just right-click QR codes in the system menu instead of manually navigating through 1Password
3. Better passkey support for native apps like Discord that expect system-level integration
4. Smoother coexistence with enterprise tools (like Microsoft Entra) that rely on system password frameworks
5. More consistent experience across Apple platforms, since 1Password already supports native integration on iOS

Users expect 1Password to work more naturally with macOS's built-in features. There's clearly strong community interest in this, as shown in several discussions:

• https://1password.community/discussion/148567/saving-of-passkeys-not-available-on-macos-sequoia-15-0-1?
• https://1password.community/discussion/comment/720451#Comment_720451

There's also extensive discussion on Reddit about why native integration would be valuable:
- https://www.reddit.com/r/1Password/comments/189999i/my_14_day_feedback_for_1password/ (this one especially goes into a lot of detail)
- https://www.reddit.com/r/1Password/comments/16tjmjt/how_can_i_save_apple_passkey/
- https://www.reddit.com/r/1Password/comments/1904lcc/apple_account_and_passkey/
- https://www.reddit.com/r/1Password/comments/11tg52u/i_cant_set_up_2fa_using_apple_passkeys/
- https://www.reddit.com/r/1Password/comments/1130yhd/native_autofill_api_on_macos_instead_of/

I think that as more apps adopt passkeys and authentication evolves, having 1Password work seamlessly with system-level features will become increasingly important for smoother UX.

ordinarybeef

Thanks for the feedback! I've passed your request to have 1Password support macOS AutoFill to the team. 🙂

You can fill 2FA one-time password using Universal AutoFill: Use Universal Autofill in apps and browsers on your Mac

-Dave

ref: PB-44050674

Would also like to see this. I don't fully get why there's so much resistance to add support for these APIs when the same APIs work fine on iOS. I want to cut out Keychain, but the 2FA autofill is very very nice. Now that it's possible to have them fill from third party managers, I want to migrate the remaining bits to 1P.

A small voice in my head is telling me this may partly due to the architecture of the mac app being in Electron instead of native ObjC/Swift, so even trivial APIs like this will need a bunch of glue/wrapper code to actually work

i am still hoping they will do add it this year....

Former Member

Thank you for the feedback, I've passed it along to the team. 🙂

-Dave

ref: PB-43124655

+1 especially now since the new apple passwords app can autofill 2fa code and passkeys in native apps.

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