- From: Emil Lundberg via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Oct 2024 12:18:28 +0000
- To: public-webauthn@w3.org
That example is described in [ยง6.2.1. Authenticator Attachment Modality](https://w3c.github.io/webauthn/#sctn-authenticator-attachment-modality): >Some [platform authenticators](https://w3c.github.io/webauthn/#platform-authenticators) could possibly also act as [roaming authenticators](https://w3c.github.io/webauthn/#roaming-authenticators) depending on context. For example, a [platform authenticator](https://w3c.github.io/webauthn/#platform-authenticators) integrated into a mobile device could make itself available as a [roaming authenticator](https://w3c.github.io/webauthn/#roaming-authenticators) via Bluetooth. In this case [clients](https://w3c.github.io/webauthn/#client) running on the mobile device would recognise the authenticator as a [platform authenticator](https://w3c.github.io/webauthn/#platform-authenticators), while [clients](https://w3c.github.io/webauthn/#client) running on a different [client device](https://w3c.github.io/webauthn/#client-device) and communicating with the same authenticator via Bluetooth would recognize it as a [roaming authenticator](https://w3c.github.io/webauthn/#roaming-authenticators). -- GitHub Notification of comment by emlun Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2164#issuecomment-2385626207 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 October 2024 12:18:29 UTC