New issue
Advanced search Search tips

Issue 870892 link

Starred by 14 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Implement support for CTAP2 clientPin command

Project Member Reported by hongjunchoi@chromium.org, Aug 3

Issue description

Implement CTAP2 client pin command functionality
 
Hi All, 
If FIDO2 external authenticator has clientPIN, on Google WebAuthN Demo https://webauthndemo.appspot.com/ the "Register New Credential" operation will do nothing after GetInfo from authenticator. 
So when will Chrome support clientPIN for authenticatorMakeCredential and authenticatorGetAssertion ?

Best Regards,
Geoffrey
fido-client-to-authenticator-protocol-v2.0-wd-20180919.pdf
1.5 MB Download
Hi Geoffrey, yes, right now Chrome doesn't support clientPIN, and any device that has clientPIN set will not be usable on Chrome (unless it's a dual Fido2/U2F device, in which case it will fall back to using U2F). You can use this bug to track progress on clientPIN support and get future updates as we implement it.
Are there any updates on when this might make it into Chrome? Having Microsoft beat you to the punch isn't a great look.
Owner: ----
Status: Available (was: Assigned)

Sign in to add a comment