- From: Rolf Lindemann via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Jul 2017 16:22:20 +0000
- To: public-webauthn@w3.org
I think this is mainly relevant in the case of roaming authenticators as bound authenticator would always be responsive (to a create call). But even without actively advertising the support for access to a roaming Authenticator on the platform to the RP JS Code, the Browser could remember that it has seen a roaming Authenticator before and could ask the user whether to use/insert it or to say no authenticator available (when encountering a create call for a WebAuthn credential). So this could potentially be addressed by implementation guidance (even without an API change). -- GitHub Notification of comment by rlin1 Please view or discuss this issue at https://github.com/w3c/webauthn/issues/503#issuecomment-313728182 using your GitHub account
Received on Friday, 7 July 2017 16:22:27 UTC