-
Jun Choi authored
According to the CTAP spec, CTAP2 authenticators will always error out when MakeCredential request with an empty "pinAuth" parameter is received to a device that has client pin already set. This prevents any users with CTAP2 devices with client pin set to use Chrome as a client. Until client pin command is implemented on Chrome, use U2F register request when possible when we know that the device has client pin set. Bug: 870131 Change-Id: Ia26d991f2b92e46c0d67625e25d88365d1d72089 Reviewed-on: https://chromium-review.googlesource.com/1159726Reviewed-by:
Jun Choi <hongjunchoi@chromium.org> Reviewed-by:
Kim Paulhamus <kpaulhamus@chromium.org> Commit-Queue: Kim Paulhamus <kpaulhamus@chromium.org> Cr-Commit-Position: refs/heads/master@{#580737}
77b5c42d