Pre-flighting breaks AppID support
jschanck opened this issue · 1 comments
jschanck commented
See Bug 1834771. I've worked around this in Firefox 115 by switching to the fallback CTAP1 implementation when AppID is present. We should check the alternate RP ID in pre-flight.
jschanck commented
After some discussion in #271, we've decided to fallback to CTAP1 when AppID is present. We also noticed that the existing CTAP2 AppID support won't work with CTAP2.1 authenticators, as the pinUvAuthToken
permissions are bound to a single RP ID. So to fix this we need to
- add a way to force CTAP1 without using the fallback implementation
- remove the CTAP2 AppID support.