- From: Matthew Miller via GitHub <sysbot+gh@w3.org>
- Date: Sun, 20 Mar 2022 01:42:24 +0000
- To: public-webauthn@w3.org
> Then I tried to see if I could customize the language based on the platform (e.g. "Complete Face ID" on a certain iPhone, "Complete Touch ID" on a different iPhone, etc.) This is what we at Duo do when presenting users with the option to use their available platform authenticator. We "brand" the platform authenticator option by looking at the user agent and intuiting the OS to then display specific names like "Touch ID", "Face ID / Touch ID", "Windows Hello"... And when we can't identify the platform (or the platform doesn't have a special name, like Android biometric) we default to calling it "this device": - "Register this device" - "Use this device to log in" I personally think the "this device" labeling is fine for all platform authenticators. It's what I'd use on personal projects if I didn't want to go through the trouble of trying to maintain branding logic. Regarding "roaming authenticators" it's getting murkier as caBLE support continues to mature. "Use security key" used to be all you needed to worry about to communicate use of a roaming authenticator, but now there's this whole angle of, "a platform authenticator usable as a roaming authenticator to auth using a single-device credential" (so you can't simply refer to it as a passkey). Still not sure how to handle that in this transitional period but maybe it's not worth fretting over for now. -- GitHub Notification of comment by MasterKale Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1708#issuecomment-1073145761 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 20 March 2022 01:42:27 UTC