3 ms·
You're suggesting that using a tunnel service is the recommended way to be a platform agnostic backend. But that doesn't cover the scenario where your password
by dcow 4y ago
You're suggesting that using a tunnel service is the recommended way to be a platform agnostic backend. But that doesn't cover the scenario where your password manager is running on the same device as the one where the user is performing the login, and all the UX/UI refers to using a phone to scan the QR code. I guess you could snag the QR code using platform accessibility features, but that's a real silly hack. Just let me advertise some mDNS service record for "authenticator" and require me to advertise a pubkey and let the user select/allow me once and remember the decision until the pubkey changes so that I'm trusted backend without the QR scanning rigamarole.
- lxgr 4y ago> the scenario where your password manager is running on the same device as the one where the user is performing the login Android will provide an API for that scenario (i.e. on-device third-party authenticators) in the near future [1]. Hopefully, iOS will do the same. [1] https://developers.google.com/identity/passkeys/supported-environments https://developers.google.com/identity/passkeys/supported-en...
- dcow 4y agoYes, I'm waiting patiently in the wings. Sadly when I asked Apple's Passkey team about supporting this, they said it wasn't on the roadmap (though they carefully didn't say never, it still doesn't instill much hope). Once this missing piece becomes a required part of the standard, I'll stop holding my breath and get super excited about passkeys.