This feature alone has made me switch to Chrome. Without PIN support for Yubikey, there really is no point in supporting WebAuthn at all, in my opinion.
Hard agree. If you've turned on Two-Factor Security with Keys for your iCloud account, every time you try to use "Log in with Apple," you're challenged for your security key. If it's PIN protected—which it should be—your login fails, so "Log in with Apple" is rendered useless.
Put it another way, without this feature, it rules out Firefox as a capable tool if pin based Yubikey is a requirement for an environment (eg corporate or other). So there will be waves of replacements of Firefox with alternative capable browsers as organizations align with best practices around MFA (especially since a swathe of recent hacks using MFA fatigue pushes organizations to choose stronger security measures like hardware tokens) and it will add to the rhetoric that Firefox just isn't a secure option vs competitors due to lack of security features, slow uptake of best practices, as more users see these features as necessary rather than nice-to-have.
I have the opposite problem now. My yubikey doesn't have a pin configured. Now firefox demands one. Defaults didn't work, guessing at 1234 or 0000 didn't work, and somehow I had the same problem when I tried to change it. Now it's locked and I have to reset it, as well as all websites I'm using it with.
I guess this is a good time to configure a pin code, as per the other comments here.
Worked on Firefox 131 but all of sudden no longer works on Firefox 132. I get prompted to enter my PIN, I enter it and still gets prompted to enter or finish the installation. Mind you, it works seamlessly on Chrome and Edge browsers on Mac. Wonder what could have been the issue here.