- From: John Bradley via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Sep 2019 20:01:34 +0000
- To: public-webauthn@w3.org
The problem is to this point applications like Brave or smartlock can't access CTAP2 over regular HID. Applications currently need to use CTAP2 over a MFi encapsulated transport using an apple lightning security chip as part of the authenticator. I hope that is not required going forward so that a standard key can be used with an adaptor. The push back we get comes from some applications that don't want to prompt the user to insert a key if it cant work. Those applications want a transports flag to indicate that a credentialID could possibly work. On iOS 13.1 or whenever WebAuthn support becomes available Applications should all use system API for invoking WebAuthn and not be talking to the lightning device directly as an accessory. The applications running on iPhone 6 etc that won't be getting iOS 13 + are really the ones at issue.and the ones that will find the hint useful. We had a number of discussions about what to call it. MFi tunnel support, lightning, tuna etc I am open to calling the flag for credentials that could work in apps on iOS12 something else to reduce potential confusion. (My preferred option was tuna) I really do hate having to specially flag things that work over lightning and USB-C on iOS 12. I hope we can come to a conclusion next week in Japan. -- GitHub Notification of comment by ve7jtb Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1294#issuecomment-530542434 using your GitHub account
Received on Wednesday, 11 September 2019 20:01:35 UTC