Safari Biometrics disabled? [SOLVED]

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

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

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.

LOL This is like when they removed access to 1Password from the share sheet. Everything was working fine. Then they update the app, and remove the feature without any prior mention of it.

Now this is the same. iOS 16 has been in beta for months, and everything was working just fine. Then, oh, WebAuthn has changed. Bollocks. This is just a boat load of rubbish. Suddenly after all these months, WebAuthn has changed last minute? As if as a developer, and a big fat one at that, 1P did not know about changes in implementation or whatever changes Apple might want to make!

Give me a break!

And look at the version number 7.9.9! What? Are you suddenly going to use a fourth digit, when you never ever did before, and make a 7.9.9.1?! Please…

You guys must really think that users are just not very intelligent.

I am going to say it :

You are voluntarily crippling the app to make people upgrade to 1P8.

Spin the PR speech like you want, but this is what it is.

LOL This is like when they removed access to 1Password from the share sheet. Everything was working fine. Then they update the app, and remove the feature without any prior mention of it.

Now this is the same. iOS 16 has been in beta for months, and everything was working just fine. Then, oh, WebAuthn has changed. Bol. locks. This is just a boat load of rub. bish. Suddenly after all these months, WebAuthn has changed last minute? As if as a developer, and a big one at that, 1P did not know about changes in implementation or whatever changes Apple might want to make!

Give me a break!

And look at the version number 7.9.9! What? Are you suddenly going to use a fourth digit, when you never ever did before, and make a 7.9.9.1?! Please…

You guys must really think that users are just not very intelligent.

I am going to say it :

You are voluntarily crippling the app to make people upgrade to 1P8.

Spin the PR speech like you want, but this is what it is.

@Jack_P_1P Unfortunately I need to insist: this is really a major, critical feature to me. Can you please route this one up the chain and make sure somebody in management sees the complaint?

Having it working this way forces me to switch to a weaker master password as I can't keep typing my complex master password all the time on a cramped iPhone keyboard. So your security reasoning regarding WebAuthn actually brings the opposite result.

I would be happy with having a hidden setting like "Developer mode" or "Advanced mode, I promise I know what I'm doing and I assume all responsibility", where we can re-enable it at our own risk. It worked throughout all the betas, up to 1Password 8.9.3. I cannot wait for an unspecified amount of time until this feature is maybe brought back. We migrated our whole company to 1Password, but we will need to consider migrating elsewhere as that's really critical.

@einsteinbqat they pulled biometrics from both 7 and 8 so that move isn’t to push people to 8.

It looks like my concerns about 1Password are coming true. All the growth bringing more negative than positive.

@more_cowbell Indeed, but whilst 1P8 will get updated eventually, I doubt that 1P7 would see any update beyond version 7.9.9.

Thanks for the prompt responses, @Jack_P_1P - and thanks for being willing to take a few arrows to keep us updated.

I’m curious why only Safari, especially as one would think that Safari would be more secure than Chrome (or other browsers) given the “marketing”

Can you provide some details on what got less secure in Safari this week (because as others have said, it was working in the betas)?

The biometric feature removal in Safari is a software regression.

My parents rely on 1Password biometric to use their passwords. Asking them to type their 1password every time they need a password filled is unacceptable.

How can the 1Password team not anticipate the security model apple proposed until the very day iOS 16 was released? Colour me unimpressed.