[Bug]: Windows 10 Hello doesn't throw a descripive error message

[cpb8010]

🧰 Project

SDK

📝 Description

The SDK expects an ES256 key from the webauthn APIs and when it's not in that expected format, the SDK fails and no descriptive error message is returned to the user. We know we can't support passkeys that aren't using ES256, so we can provide a much more descriptive error message if we can't prevent the browser from returning data that we can't use!

🔄 Reproduction steps

On a windows 10 machine, use the Windows Hello PIN or facial recognition options to create a passkey in the auth server creation page. You'll get a generic error, and the console logs will show that we're expecting a value that doesn't exist in the passkey data.

🤔 Expected behavior

We return an error message that says something to the effect of "We don't support Windows 10 Hello, try any other passkey provider!"

😯 Actual behavior

People think it's broken and they can't sign up.

🖥 Environment

Windows 10 or Windows 11 before the 2022 update.

📋 Additional context

Eventually we might want to support RS256 and Windows Hello for Windows 10, but for now it's not a high priority since we expect most users will want to use their mobile devices for passkeys due to their portability and integrated backup options.

📎 Logs

DqOc5i10.js:1  DataError: The JWK "n" member contained a leading zero.