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

@bzbarsky wrote:
> I think the idea is to not call the relevant #createCredential at all if the corresponding member is not present in CredentialCreationOptions, right?

Correct, as @emlun [notes above](https://github.com/w3c/webauthn/issues/750#issuecomment-426970949).

@emlun wrote:
>  I don't think we really need to do much more here.

Agreed, given @bzbarsky's [comment above](https://github.com/w3c/webauthn/issues/750#issuecomment-424946912).

>  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.

Agreed. As I [noted above](https://github.com/w3c/webauthn/issues/750#issuecomment-407238236), that issue is now forked over to issue #1004.

So, are we good with closing this issue #750?

-- 
GitHub Notification of comment by equalsJeffH
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/750#issuecomment-427108343 using your GitHub account

Received on Thursday, 4 October 2018 17:44:11 UTC