[Webkit-unassigned] [Bug 191516] [WebAuthn] Support CTAP Client Pin

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=191516

login Llama <loginllama at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |loginllama at gmail.com

--- Comment #2 from login Llama <loginllama at gmail.com> ---
Yes for keys with PIN set you cant create new credentials without the user inputting the PIN in CTAP2.   The workaround that Firefox and Chrome use when UV is set to discouraged is to make the credential using U2F on keys that support both CTAP1 and CTAP2.  For a CTAP2 only key or if you are making a resident credential there is no way to do it without PIN support.

I will note that currently CTAP2.1 will allow the creation of non resident credentials via CTAP2, but there are millions of authenticators in the market currently that will only support CTAP2.0.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20191213/d7df3c00/attachment.htm>