Please consider integrating 1Password as a Credential Provider on macOS.

Well, passwords go beyond the browser 1P_Dave. Many apps are launching web browser windows to let you sign in. On macOS this is just a WebKit browser window, without any plugins. In this case when a passkey is requested, ONLY the system can respond and any passkeys saved in 1Password would not be available to use.

Additionally, apps could want to let you sign in with a passkey directly, without a browser window. This is another situation in which 1Password is not able to provide the passkey, because the it doesn't integrate with the system.

It's just sad to see 1Password doesn't want to integrate with the system and leave users without the ability to sign in with passkeys in certain situations. Passkeys should be available whenever a user needs them, not only when the browser extension is installed.

Hi Dave, thanks for your response.

Yes, macOS AutoFill doesn't over all of the features. But that hasn't stopped you on iOS/iPadOS, there you can choose to use the browser extension and/or AutoFill. Also consider that 1Password AutoFill is not on by default, users have to enable this in settings. So users always have the option to either use the extension or use autofill, they have to pick.

I'm not saying to drop the extension and only go forward with AutoFill on Apple devices, but why not offer the option? Users who know the advantages will enable it and those who want everything 1Password has to offer can install the extension or use Universal AutoFill.

As for the password popup problem, I solved it with the advise you gave to use separate browsers. Chrome for work, Safari for personal. Although if 1Password will ever support macOS AutoFill I would instantly drop Chrome and just use Safari for everything.

Ahh... right. So you are essentially saying I cannot use 1Password to sign me into an app using a passkey on my Mac without using another device. A credential manager not being able to sign me in, imagine that!

A major point of passkey is speed, having to grab my phone, scan a QR code, wait for the devices to connect to then be able to sign in takes a lot of steps, a lot of steps that could have been avoided had 1Password integrated as a credential provider like on iOS/iPadOS.

And all this for a board member of the Fast Identity Online Alliance, your current solution is slow by design.

1Password has this big stance on moving away from passwords, 1Passwords wants to move to passkeys and they see it as the future. Then why make it harder for macOS users to sign into apps and have all these hacks and extensions when you could just integrate with macOS?

You currently have 3 flows:
- Signing in with a password on a website in a browser: use the extension
- Sing in with a password on something like a Safari Web App: Use this weird accessibility hack we made
- Sign in to an app or Safari Web App with a passkey: oh we can't do that at all, use another device.

All this could be replaces by integrating with the system and provide one seamless flow that is always consistent and works on all devices.

+1, add my vote in as well.

This thread has outlined many usability improvements already by integrating 1Password as a credential provider in macOS, but I want to add one. On iOS 17 and aligned releases on their other platforms they introduced a capability where you can pick a username/password from iCloud Keychain in any textfield in cases where the system did not detect it as a username/password field. On the new beta's (iOS 18 and aligned releases) Apple is opening this up so other credential providers, like 1Password, can also fill out credentials in textfields that were not detected as a username/password field.

This would then also be a benefit on macOS.

Just wanted to mention that I have been hoping to see this feature being integrated.

We use Microsoft Intune for MDM, which does not integrate well with macOS, especially during device onboarding.
Whenever I set up a macOS device for a new employee, there are three or four, maybe five, separate sign-ins, all in private webkit windows. This is a hassle.

Passkeys make this process so much easier. But using 1Password passkeys means having to have a separate device configured, which isn't much of an improvement to be honest. So I stick to physical security keys instead.

As an aside, I cannot for the life of me figure out how to get Microsoft 365 passkeys in 1Password to work. If you have any advice on that, please let me know, because Microsoft is doing something weird, and i can't figure it out.

Whenever I set up a macOS device for a new employee, there are three or four, maybe five, separate sign-ins, all in private webkit windows. This is a hassle.

You'll want to look into Intune's Platform SSO to fix that problem. It's recently gone GA.

When deploying devices via the Apple Device Enrollment (ADE) route and user-affinity, they sign in once to a Microsoft 365 account at the OOBE to assign the device to them.
Then they enter a macOS username and password at setup assistant. Once on the desktop, the click the prompt to register their device with Platform SSO and sign into their Microsoft 365 account, once that's completed all other Microsoft 365 sign-in screens log them in automatically (in applications using the right authentication libraries), and browsers like Safari, Microsoft Edge and Chrome (all with some pre-reqs).

aksel

Thank you for the feedback. Let us know if ajh0912's (thanks for jumping in!) suggestion helps. 🙂

-Dave

ref: PB-41721971

Hello martijnvdwal! 👋

Thank you for the detailed feedback! I'm not personally aware of plans to support macOS AutoFill and the team is focused on 1Password in the browser and Universal AutoFill. I believe that macOS AutoFill doesn't offer support for many of 1Password's features such as its advanced filling brain, password generator, masked email aliases, sign in with, and more. That being said, I've passed your request along to the team internally.

For the time being, 1Password isn't designed to be used alongside another password manager in the same browser and I would usually recommend using different browsers for work and personal matters. You could continue to use Safari for personal things and try another browser like Chrome or Firefox for work. This would also allow you to keep personal and work matters separate.

I also wanted to mention that, if your workplace is using 1Password for Business, then you might be eligible for a free 1Password membership for you and your family: Get a free 1Password Families membership when you use 1Password Business

Thanks again for the suggestion. 🙂

-Dave

ref: PB-38634947

martijnvdwal

Thanks again for the feedback, I appreciate that you took the time to voice your thoughts and I've passed them along to the appropriate team.

For the time being, for apps/browsers that don't support 1Password, you can use 1Password on your mobile device to sign in to the app or website by choosing iPhone, iPad, or Android device and then scanning the resulting QR code using your mobile device's camera:

This will allow you to use your saved passkey in 1Password to sign in to the service or app in question. I hope that helps.

-Dave

martijnvdwal

Thank you for the feedback, I've merged your other comment into your existing thread so that we can keep the conversation in one place. The native AutoFill feature in macOS doesn't support all of the features that 1Password offers which makes completely replacing our extension with it a non-starter. These features include but are not limited to:

• Filling identity and credit card items.
• SSH key generation.
• Compatibility with integrations like Privacy.com and Fastmail masked email aliases.
• Use of 1Password's own filling brain.
• Support for features like sign-in with, autosubmit, and 1Password's standalone password generator.
• Smart/Memorable password generation right on the page using 1Password's password generator.
  

Replacing 1Password's browser extension with macOS AutoFill limits what 1Password can do to only the features that Apple decides to add to macOS AutoFill. That being said, I have filed a feature request with our team to look into expanding support for passkey saving and sign in in Safari Web Apps and other desktop apps. The team will consider all options, including macOS AutoFill.

On iOS 17 and aligned releases on their other platforms they introduced a capability where you can pick a username/password from iCloud Keychain in any textfield in cases where the system did not detect it as a username/password field. On the new beta's (iOS 18 and aligned releases) Apple is opening this up so other credential providers, like 1Password, can also fill out credentials in textfields that were not detected as a username/password field.

I'm glad to hear that this is now working with third-party password managers. It's a common point of confusion for folks who have disabled iCloud Keychain for iOS AutoFill but still see it when double-tapping on a field and then tapping on AutoFill.

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.

This sounds like you might have both iCloud Keychain and 1Password enabled in Safari which is causing a conflict. Can you try these steps:

1. Make sure that 1Password is set as a default password manager in Safari and that the built-in password manager is turned off: Turn off the built-in password manager in your browser
2. Click on the  in the menu bar and then clicking System Settings.
3. Click Passwords.
4. Click Password Options.
5. Turn off "AutoFill Passwords and Passkeys".

Then try to sign in with a passkey again: Save and sign in with passkeys in your browser

Let me know how that goes. 🙂

-Dave

ref: PB-40546086