Why would you choose that over a synchronizing passkey manager?

A third party OAuth provider puts you at the mercy of the service provider, the other can work fully on your client side even if the app provider were to disappear tomorrow.

The only advantage I can think of is that you have a centralized place to revoke credentials in case your password manager does get compromised.

▲

iamnothere an hour ago | parent | next [-]

> Why would you choose that over a synchronizing passkey manager?

No second factor, compromised passkey manager leads to compromise of all accounts. This is a huge problem.

> A third party OAuth provider puts you at the mercy of the service provider, the other can work fully on your client side even if the app provider were to disappear tomorrow.

Yes that’s what I was saying, it needs some thought and careful work. It would need to be decentralized, and I’m not sure that current standards are up to the task.

▲

UltraSane 42 minutes ago | parent | prev [-]

"A third party OAuth provider puts you at the mercy of the service provider" This is they key issue with trusting a third party to manage my passkeys, they can also BLOCK them and lock me out. An exception is if the passkeys are synced to all your devices and cannot be remotely wiped. I think this is how Apple works.

	▲	iamnothere 31 minutes ago \| parent [-]
		I didn’t think of this in the moment, but you’re right, this is an even bigger risk than compromise. There’s regularly a thread here about someone getting locked out of their cloud accounts, and now we’re going to gate everything behind those same accounts? Horrible idea.