Tim Cappalli

IMO, this should go in FIDO Alliance deployment guidance, not the WebAuthn specification, but I'd be interested to hear others' opinions on this.

Please update the title and original description to more accurately represent the ask.

Known issue: https://github.com/solokeys/solo/issues/499

No worries! Glad more people are reporting it. I will add the error text from Microsoft Account to the other issue so it comes up in search.

> Just stumbled upon this today, sadly still not supported. I wanted to use my SOLOkey in Azure. New link for the certification: > https://docs.microsoft.com/en-us/azure/active-directory/authentication/concept-fido2-hardware-vendor Yes, the process outlined in...

@bbangert, these UX considerations will eventually be covered on passkeys.dev. They don't belong in a specification.

@bbangert, what you're asking for is not possible today. Many RPs prompt the user for a nickname or just try to derive it via client hints + attachment. For passkeys...

3 concerns I have from the 2024-03-27 meeting: 1. UP and UV are not occurring during the WebAuthn create ceremony 2. There is no binding between the autofill provider and...

Here's a proposal based on the discussion and concerns expressed yesterday: - When conditional create is used, UV and UP **MUST** be `0`/`false` unless UP or UV is performed as...

The verification step needs to be updated as well to add an if mediation=conditional check. `1. Verify that the [=UP=] bit of the [=flags=] in |authData| is set.` https://github.com/w3c/webauthn/blob/89f204f4b1b02a147dfcdee4fbd88319cab5e104/index.bs#L5372