Re: [webauthn] Credential Creation Options are inconsistent to Request (#1716)

A really good example is that we may only want a specific vendor of usb authenticators to be used - then there is no need to display options for caBLE which in fact will confuse users "why can't I register my phone". 

As well, we *have* these options for authentication today, why are the not able to be consistent? 

> but report their [getTransports()]( as ["ble", "internal"] regardless of how they were attached during registration. That should resolve most of the ambiguity around those being both platform and cross-platform credentials depending on context.

The issue here is you need to do a full registration cycle to getTransports() and *then* the RP can reject this, which will annoy the user more.

GitHub Notification of comment by Firstyear
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Tuesday, 5 April 2022 22:40:36 UTC