- From: Adam Langley via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Sep 2019 23:45:21 +0000
- To: public-webauthn@w3.org
> So assuming iOS WebKit's support for USB authenticators via lightning also worked through USB-C and USB-A dongles, would it make sense to merge it into the generic "usb" transport?
The transports are purely to enable smarter client-side behaviours, so I don't believe that having an enumeration for Lightning hurts anything. If it's truly useless, then clients will simple end up ignoring it.
Here's an example of where it might be useful, even in a world where iOS works with USB authenticators attached via a dongle: If an iOS client receives a GetAssertion that has a credential with transports {USB, NFC} then, on an iPhone, guiding the user to use NFC is probably the way to go because Lighting↔USB dongles aren't that common. However, if the transports where {USB, NFC, Lightning} then the client would probably be better off suggesting to use the Lightning connector.
--
GitHub Notification of comment by agl
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1294#issuecomment-529709147 using your GitHub account
Received on Monday, 9 September 2019 23:45:23 UTC