Native Password AutoFill Extension macOS

I want to second the other comments in this thread that explain why native autofill would make for a better user experience. But I'm also troubled by the fact that the two alternatives offered for Mac users require either 1) a Safari extension that can read and alter every web page that I visit or 2) permission to view and control everything that happens on my computer. Yikes! Yes, I realize that we are already placing a lot of trust in 1Password. But I'd expect a security focused company to understand the principle of least privilege. The native autofill API is not just the best user experience -- it's the most secure solution.

Strongbox uses the native api implementation. It is one of the things I missed more when I switched to 1P and having my wife as she it worked best for her workflow.

1P_Dave

Thank you for your prompt response. In regards to your two points:

1. You are absolutely right about the webapps. I was mainly talking about apps that come in a native container, but use embedded web technolgies such as electron for the whole app (such as Microsoft Teams) or at least the login/SSO part. Especially the latter is very important for me because a lot of my work stuff integrates with Azure AD. Those apps all work with password entry and passkeys via the native implementation. I have checked with passkeys in iCloud Keychain and a colleague tells me that something called Strongbox (?) works as well. On the other hand with 1P you are out of luck because you can't install extensions in these 'native' apps.
2. The most annoying cases in which Universal Autofill hasn't worked for me are Cisco Jabber and Webex, although at least in Webex this has been fixed in the latest version. It also does not work in vmware Remote Console and something called PP3D (this is B2B tooling, I don't think it is publicly available). My theory is that those things do something to prevent input via the Acessiblity features of macOS because of some security policy? Or maybe just a badly configured SSO? Whatever it is, the native password integration just works.

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:

• Saving of Passkeys Not Available on MacOS Sequoia
• macOS Sequoia Autofill

There's also extensive discussion on Reddit about why native integration would be valuable:
- My 14 day feedback for 1Password (this one especially goes into a lot of detail)
- How can I Save Apple Passkey
- Apple Account and PassKey
- I can't set up 2FA using Apple Passkeys
- Native Autofill API on macOS instead of Accessibility hack?

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....