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

jason13's avatar
jason13
New Contributor
4 months ago

macOS Sequoia Autofill

I've seen some places in this forum where you guys have informed people that 1Password doesn't use the macOS autofill settings. I was just curious if there are technical reasons that prevent you from using this, or if there are specific design reasons for not adopting it, or if it's something that's coming in a future update. It seems like the native autofill integrations would be the best option, but maybe not.


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: macOS 15.1
Browser: Not Provided

  • milp00l's avatar
    milp00l
    New Contributor

    I'm not saying 1Password doesn't work. It does. I'm saying it's confusing to me and many others that it doesn't show up in this screen, and that it can't be selected in "Set Up Codes In".

     

  • Hello jason13! 👋

    Thanks for reaching out! 1Password supports two different filling methods:

    1. 1Password in the browser (the browser extension): Get to know 1Password in your browser
    2. Universal Autofill: Use Universal Autofill in apps and browsers on your Mac

    These filling methods both use the 1Password filling brain which means that we're able to correct issues as they're reported to us, something that we can't do with macOS AutoFill. 1Password in the browser also allows us to support many of the features that folks use with 1Password such as masked email aliases, integrations with services like Privacy.com, SSH key support, and more.

    That being said, we have received requests to support the macOS AutoFill feature. Is there a particular use case, where the current methods fall short, that makes you personally interested in seeing macOS AutoFill being supported in the future?

    -Dave

  • jason13's avatar
    jason13
    New Contributor

    I was mainly curious about y'alls rationale. I saw that you made updates to the iOS/iPadOS autofill functionality (though maybe those changes aren't directly tied to new iOS 18 functionality) and was wondering why you didn't also do it on the Mac side.

    I have run into the Discord issue mentioned in another thread where you can't sign in with a passkey, because it's only looking at the native integration. Not sure if that's a Discord implementation problem or how Apple expects it to work. But as more and more apps adopt passkeys, I'd assume we might see a similar issue more often.

    I also have my Mac linked to a Microsoft Entra directory, and my company has implemented the new Platform SSO feature, which directly integrates with the native system to support passkeys. So the native autofill has to be enabled so that the Microsoft Company Portal app's authenticator element can function. Given that y'alls recommendation is to completely turn off autofill, this can create a conflict between the two systems. This is a newer requirement/implementation for my company, so I haven't experienced a ton of issues so far, but I'd imagine they could come over time. It was problematic on iOS 17 when you could only select one 3rd party autofill app, and I sometimes had to change that setting from 1Password to Microsoft Authenticator temporarily and then switch back. iOS 18 has simplified that since both apps can be enabled at once.

    I didn't think about the masked emails, I'm guessing there's no way to use native methodologies to take over the iCloud Hide My Email button or present 1Password's option right next to it?

  • jason13

    Thanks for the reply. iOS is much more locked down than macOS is which means that 1Password needs to rely more on iOS AutoFill. For example, only Safari on iOS supports extensions which is why the 1Password extension is only available for that browser on the iPhone and iPad.

    macOS, on the other hand, offers more options and allows 1Password to support two different filling methods:

     

    Because the team already supports two different filling methods there hasn't been as much priority given to supporting a third filling method. That being said, there are some use cases that customers such as yourself have reported where integration with macOS AutoFill could be helpful and the team is tracking those use cases. I've filed a feature request on your behalf as well.

    I also have my Mac linked to a Microsoft Entra directory, and my company has implemented the new Platform SSO feature, which directly integrates with the native system to support passkeys. So the native autofill has to be enabled so that the Microsoft Company Portal app's authenticator element can function.

    The team would be interested in learning more about this. Could you have your company's IT team reach out to your account manager or our support team at support@1password.com to discuss this in more detail. We'd love to learn more about how we can support this use case.

    -Dave

    ref: PB-44051293

    • milp00l's avatar
      milp00l
      New Contributor

      I came here having searched around, trying to find an answer to this too. Look at these other threads asking essentially the same thing:

      https://www.1password.community/discussions/1password/1password-autofill-options-on-macos/88688
      https://www.1password.community/discussions/1password/how-can-i-get-rid-of-the-new-since-sequoia-pop-up-enable-password-autofill/90879
      https://www.1password.community/discussions/1password/macos-15-1-and-using-1password-as-default/128391

      People are clearly confused about why 1Password isn't there. I understand this is just my opinion, but I think the amount of confusion caused by the fact that we can't select 1Password for macOS Autofill is pretty high. And it seems worth it to me to enable 1Password's presence in that menu if only to reduce confusion amongst your users. I've probably spent at least an hour total trying to "fix" this, and searching for an answer. I'm sure many other hours have been spent by others for the same reason. 

      Beyond that, it seems like some people might view the presence of Apple's Password's app in that menu to be a recommendation of it, and view 1Password's absence as something lacking in 1Password.

      I really do think it's worth serious consideration.

  • Perhaps I am not understanding the issue, but I have not had any issues using the macOS or iOS Autofill.

    1Password Settings

     

    Chrome Settings

     

    1Password's Safari Settings (right-click extension > Settings)