Hi all, I'm working with a few different FIDO2 devices and noticed recently some different behavior between an custom device (let's call it DeviceA) and a Yubikey that was not present before.
The issue is that when setting the PIN for the first time on Chrome on MacOS, if I enter a PIN that is too short, it fails in a non-descript way on DeviceA, while on the Yubikey, the Chrome prompt indicates that the pin was too short.
I'm guessing it has something do with the fact that DeviceA is CTAP2.0 only and cannot specify a min pin length in the authenticator info, while the Yubikey is CTAP2.1. However, when I test this using fido2.ctap Python library, both return error 0x37.
Does anyone have a better understanding of what the key management in Chrome is doing and if there is some reason that it's no longer able to prompt for longer pin on DeviceA?