Skip to main content
October 9, 2023
Question

Disable Passkey support for AutoFill

  • October 9, 2023
  • 16 replies
  • 1755 views

I prefer to keep Passkeys in my iCloud Keychain because it's essentially syncing just on my iPhone & iPad, while 1Password has an archive file format, so those keys would essentially be files in the filesystem on my Windows PC.

The problem is that in iOS 17 I have to have both enabled for that. I liked the behavior back in iOS 16, where 1Password didn't declare Passkey support (because there was no API) and iOS auto-picked iCloud. Can that be added as an advanced switch to the app? Or does iOS 17 not allow password managers to declare Passkey support dynamically? (i.e. it's stuck in the manifest and can't be changed)


1Password Version: 8.10.16
Extension Version: Not Provided
OS Version: iOS 17.0.3
Browser: Not Provided

16 replies

1P_Dave
1Password Employee
October 20, 2023

@effata

Thank you for adding your suggestion. I would also be curious to hear from you about why you save passkeys in iCloud Keychain and passwords in 1Password, why not just keep everything in one place protected by 1Password's end-to-end encryption and security?

-Dave

November 22, 2023

In my case, I want to continue using a yubikey for some accounts, not iCloud.

It is inconsistent that this appears to be a supported option on every platform on iOS, and bluntly the responses saying to just use 1password instead are a little tone-deaf and feel like the infamous "you're holding it wrong".

November 22, 2023

To give one example though: if I register a yubikey with discord, for example, I can then log in to Discord on a machine I don't trust enough to put a 1password installation on to. I could create a separate account with a shared vault, but that counts towards my plans' account limits, is more work, and requires storing my passwords and second factor in the same place.

1P_Dave
1Password Employee
November 23, 2023

@fredemmott

Thank you for the feedback! Just to clarify, are you using the YubiKey as the single source of authentication for Discord? Or are you using the YubiKey for two-factor authentication after entering your password?

If it's the latter then you should still be able to use the YubiKey for two-factor authentication even if 1Password is set as the provider of passkeys on your iPhone/iPad. Is this not working? What do you see when you try to use the YubiKey when signing in?

-Dave

November 23, 2023

Sorry, Discord was a bad example; it's a second factor, as a non-resident key. The previous version of the Discord iOS app attempted to register resident single-auth-method passkeys, but this appears to be a bug as it was not possible to log in with them on any platform, and after their update, they register non-resident as a second factor everywhere.

There are several sites (e.g. github) which support resident passkeys where I use a yubikey as the sole authentication method, and the current iOS implementation of 1password makes this extremely awkward. This really feels like an oversight in the iOS app given that:

  1. turning this feature off is documented at https://support.1password.com/save-use-passkeys/#get-help - but the article does not mention that the option does not exist on iOS.
  2. the option to turn the feature off exists and works fine in the Windows and Mac 1password apps.

There is nothing fundamentally different about my requirements for passkeys on Windows/Mac and on iOS, and a cross-platform password manager should have consistent cross-platform behavior.

1P_Dave
1Password Employee
November 23, 2023

@fredemmott

I'm sorry for the confusion. The article that you linked to is for 1Password in the browser, our extension for desktop browsers.

On the iPhone, passkeys are saved and used with iOS AutoFill rather than our browser extension which is why you're not seeing the same option there. You can find our guide on using iOS AutoFill here: Use 1Password to save logins and sign in to apps and websites on your iPhone and iPad

That being said, thank you for the feedback. I've passed your request along to the team internally so that they can look into this further. 🙂

-Dave

ref: dev/core/core#24139
ref: 37012221