- From: Shane Weeden via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 Oct 2021 01:47:10 +0000
- To: public-webauthn@w3.org
I don't see a spec issue here. If a bug is suspected in Chrome, perhaps that is better reported at https://bugs.chromium.org/ The use of transports in WebAuthn is a hint to browsers, *optionally* available as part of the credential descriptors in an **allowCredentials** list during `navigator.credentials.get()`. The idea is that browser may be able to optimise the UX based on the transports value of credential descriptors defined in allowCredentials. If no allowCredentials list is supplied, then: - by definition there are no transports available to optimise the UX based on the characteristics of the authenticator that the user may have and - only discoverable *credentials* (not authenticators) may be used Not all browsers support getTransports() - that will come down to the version of WebAuthn supported in a browser-specific implementation (getTransports() was only introduced in L2). It is not required that transports be included as part of public key credential descriptors in an allowCredentials list (this is an optional member). When however these things are available and included with an allowCredentials list in an authentication ceremony, it does permit an optimised UX. -- GitHub Notification of comment by sbweeden Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1677#issuecomment-950455394 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 25 October 2021 01:47:12 UTC