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

+1000 for using the native macOS/iOS APIs for Autofill. iCloud Keychain is quickly becoming a superior filling experience.

1P_Dave Using passkeys for Safari Web Apps is one big example, and it's frustrating me too. The browser extension is also plagued with connection reliability issues (at least with Safari) and has been for some time. I don't know why 1Password has been so stubborn to adopt the great API built into macOS as they already have adopted on iOS.

Thanks 1P_Dave – and you're right on iOS, but the iOS API integration did take a step backwards with the release of 1Password 8. Unfortunately, 1Password no longer respects the "Enable/disable Face ID for Autofill" setting in iOS Settings. Now, even if you have that set to disabled, 1Password insists on launching its extension and performing auth before filling the credentials. And on macOS, the current implementation of passkeys in the beta extension is not promising. It's implemented without the macOS APIs and attempts to hijack the system passkey prompt instead of just integrating with it.

I think michaelyork summed it up best for me. "Stubborn" is the path you chose XD 1Password is great software, and on the Mac the past year has shown that the Credential Provider API is the best way forward to offer a seamless integration for all things passwords and passkeys on Apple platforms. It may diverge from the path forward you originally carved with the 1Password Universal Autofill hack, but please accept that most people really appreciate Apple native integration. :)

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

Native Password AutoFill Extension macOS

1P_Dave
Moderator
5 months ago
Former Member

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

-Dave

ref: PB-43124655
Former Member
5 months ago
+1 especially now since the new apple passwords app can autofill 2fa code and passkeys in native apps.
1P_Dave
Moderator
12 months ago
jhogervorst

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
jhogervorst
New Contributor
12 months ago
➕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 split off, for visibility.)

One use case for native macOS AutoFill are the new Safari 17 web apps, 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
Moderator
2 years ago
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:

Get to know 1Password in your browser

Use Universal Autofill in apps and browsers on your Mac

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
okapica
New Contributor
2 years ago
+1 The feature is already supported in IOS and iPadOS. Integration should work without the need of accessibility features which Universal autofill relies on.

*edit with a French Canadian keyboard mapping universal autofill with CMD+\ is convoluted.
t3rminus
Occasional Contributor
2 years ago
+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.
OAW
Frequent Contributor
2 years ago
+1 on this feature. Consistency within the Apple ecosystem is always preferable.
1P_Dave
Moderator
2 years ago
billimek

Can you tell me a little more about your use case for the feature? Knowing more about where the current filling options (1Password in the browser and Universal Autofill) are falling short for you will help our product team better prioritize the request. 🙂

-Dave
billimek
New Contributor
2 years ago
Please add my voice to the request for native MacOS password autofill integration!