Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
snowy
3 years agoFrequent Contributor
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
- michaelyorkOccasional Contributor
+1000 for using the native macOS/iOS APIs for Autofill. iCloud Keychain is quickly becoming a superior filling experience.
- michaelyorkOccasional Contributor
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.
- michaelyorkOccasional Contributor
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.
- iantoOccasional Contributor
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. :)
- t3rminusOccasional Contributor
+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.
- JonsaWoterusNew Contributor
+1 on this feature. Just to get passkey support for native apps without having to resort back to qr-codes and your mobile
- cyt233New Contributor
+1 on this feature. By supporting native autofill on macOS, 1password users will get better passkey and SMS code autofill experience. it can also make it possible to use 1password with other password manager. why not support this feature to make 1password more perfect. i don't think it is a feature that can not coexist with current autofill implementation
- snowyFrequent Contributor
To clarify Universal autofill doesn’t fulfill the need described above.
Universal autofill requires accessibility permissions. In this case this permission change is not allowed.
The second part it doesn’t show in-line with iCloud Keychain entries. One for usability and second in the case of sharing with who uses both and forcing this person all in 1Password is not an option.
- snowyFrequent Contributor
so I saw the recent post from 1password about the native autofill with passkeys for iOS 17:
Interesting the link in the blog post:
https://developer.apple.com/passkeys/
It shows macOS using this native autofill option, but 1Password post only makes reference to iOS in regards to the apple platforms. I hope 1password will consider this implementation for the Mac. Particularly in terms of being consistent across platforms. It is much easier to explain to my spouse to just turn on autofill across the devices using native function while 1Password remains the secure store for passwords and passkeys.
- iantoOccasional Contributor
Another +1 for me. I would really miss 1Password because it holds more than just Passwords (or Passkeys in the future for me), but without native Autofill instead of the Universal Autofill hack, I need to migrate away.
I don't mean to sound so final, but it is a dealbreaker for me, not just a nice-to-have.
In addition to being well-integrated, it is also blazingly fast with amazing user experience. The 1Password extension takes seconds to even appear, and sometimes up to 10 seconds to even unlock and react.