Safari Biometrics disabled? [SOLVED]

Can’t continue taking away features and expect us paying customers to stick around. Taking it away without a plan is a joke. 1Password is losing the trust of many long time and loyal customers that helped you build what was a great product.

I love emotionless, corporate speak almost as much as I love paying a subscription fee for an app that continues to remove features.

Hi @ManuCH:

After doing some further investigation with the way WebAuthn works in iOS 16, allowing for Touch ID or Face ID unlock for 1Password for Safari created a less secure environment than we were comfortable with. Because security is our top priority, we disabled the feature until we can find a suitable replacement.

@Nicholas1P:

I'd love to see the return of Face ID or Touch ID unlock to 1Password for Safari as well, but as it currently stands I don't have any timeframes to share just yet. Thanks for your feedback!

Jack

Hope this doesn't take too long to fix.

Jack_P_1P Why do you need to work with your partners at Apple, if this worked until a few hours ago, before you released the update, on iOS 16 RC, which I've been running for a week? Can you please share more details? This just doesn't add up to me. It worked, yes, with IOS 16, and you removed the feature?

Hi AMonitorDarkly:

Yes, that's correct. This change only affects unlocking the 1Password Extension on iOS for Safari using Touch ID or Face ID, and you can continue to use biometrics to unlock 1Password when tapping "🔑Passwords" or "🔑" above your keyboard.

more_cowbell / @ManuCH:

As I mentioned above, we're working with our partners at Apple, but I don't have any specifics to share at this time.

@mackg:

We used WebAuthn with 1Password for Safari to enable you to use Face ID or Touch ID to unlock. The changes to WebAuthn in iOS 16 don’t align with our security model and aren’t compatible with our implementation of WebAuthn. Consequently, we’ve removed this feature for now.

deviantintegral:

This change would only apply to 1Password for Safari itself, and not filling using Password AutoFill, as I mentioned above. We have crafted your 1Password experience to be as consistent as possible across operating systems. We also don’t want 1Password to be the reason for not upgrading to iOS 16. We are talking to our partners at Apple about how we can bring this feature back.

Jack

Does this only affect the Safari extension, or does it also affect the system-level filling that can be used in Safari? Is it only disabled for those upgrading to iOS 16?

To me that's unacceptable. That's one of the main features going missing, which by the way was working perfectly before the upgrade on iOS 16 RC. Can we have that enabled again like it was before?

This doesn’t appear to affect auto-fill though, is that right?

Dupe