- From: Nesuma via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Jun 2020 08:07:37 +0000
- To: public-webauthn@w3.org
What I meant is a theoretical scenario where you have registered a device as authenticator and the device itself does not support any form of roaming authenticator (no USB, Bluetooth, NFC, etc.). How would you be able to register another device if there a no token that you can use to bridge the gap between the devices? As far as I can tell there is no way to successfully register another authenticator (and therefore device) in this case, so you could only use the second device after disabling webauthn on the first device and registering the second device. But now you can't register the first one again. I think that this scenario is mostly theoretical because most devices have multiple interfaces for roaming authenticators but I still wonder if this case is handled in a defined way -- GitHub Notification of comment by Nesuma Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1429#issuecomment-637368212 using your GitHub account
Received on Tuesday, 2 June 2020 08:07:39 UTC