W3C home > Mailing lists > Public > public-webauthn@w3.org > July 2018

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

From: =JeffH via GitHub <sysbot+gh@w3.org>
Date: Mon, 09 Jul 2018 21:14:16 +0000
To: public-webauthn@w3.org
Message-ID: <issue_comment.created-403622614-1531170854-sysbot+gh@w3.org>
> I _think_ it happens [here](https://w3c.github.io/webappsec-credential-management/#algorithm-create), where _interfaces_ refers to [here](https://w3c.github.io/webappsec-credential-management/#credentialrequestoptions-relevant-credential-interface-objects) where _options_ is the options argument object sent to the `create()` method and the `[[type]]` slot for the [PublicKeyCredential][pkc] interface contains `"public-key"`.

[IIUC](https://en.wiktionary.org/wiki/IIUC), the above is correct.

> ...actually, does that mean that the publicKey member name in CredentialCreationRequestOptions should also be "public-key", or vice-versa?

IIUC, I do not think that the difference between the `[[type]]` slot's value of `public-key` and the  [CredentialCreationOptions](https://www.w3.org/TR/webauthn/#credentialcreationoptions-extension) and [CredentialRequestOptions](https://www.w3.org/TR/webauthn/#credentialrequestoptions-extension) dictionare extensions' member name of `publicKey` causes any issues. 

cc: @mikewest 



-- 
GitHub Notification of comment by equalsJeffH
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/750#issuecomment-403622614 using your GitHub account
Received on Monday, 9 July 2018 21:14:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:58:52 UTC