- From: Akshay Kumar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 May 2018 23:33:39 +0000
- To: public-webauthn@w3.org
We have authenticators which support multiple transports. Relying on user to always use the same transport may not be the best choice. Directing the experience on what was used in Make Credential is not something that can be relied upon. For example, lets say user provisions the key on NFC reader on one machine. Then it roams around to a different machine where there is no NFC reader and it breaks down. But user wants/can use USB. Relying on transport information during MakeCredential and making decisions based on that is not a good design. Also, I would like RP's not to be burdened with this new caveat. Rp will not understand this and can make wrong choices. -- GitHub Notification of comment by akshayku Please view or discuss this issue at https://github.com/w3c/webauthn/pull/882#issuecomment-385820875 using your GitHub account
Received on Tuesday, 1 May 2018 23:33:48 UTC