- From: David Waite via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 May 2019 23:28:10 +0000
- To: public-webauthn@w3.org
One specification for roaming authenticators is supplied by the FIDO alliance, in the form of [CTAP](https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-client-to-authenticator-protocol-v2.0-id-20180227.html). Support to talk via CTAP to roaming authenticators is implemented by the client or platform - there are implementations shipping within Firefox, Chrome, as well as in the Android and Windows platforms. The client interface provided by Web Authentication is meant to hide details of how an authenticator is communicated with - details on whether an authenticator is a roaming authenticator and what transports it supports are really provided for relying party user experience. -- GitHub Notification of comment by dwaite Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1221#issuecomment-495419968 using your GitHub account
Received on Thursday, 23 May 2019 23:28:12 UTC