Re: [webauthn] `CredentialRequestOptions` make otherwise valid values invalid in an undesirable way

>The spec needs to define what happens when the `publicKey` member is not present. [...] I _think_ the idea is to not call the relevant #createCredential at all if the corresponding member is not present in `CredentialCreationOptions`

Yes, I think that behaviour is implied by the CredMan spec (see and the subsequent few comments), so I don't think we really need to do much more here. As far as I can tell, the one thing we _do_ need to figure out in order to integrate correctly with CredMan on this is to align the `"public-key"` type value and the `publicKey` member name.

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

Received on Thursday, 4 October 2018 10:43:06 UTC