- From: =JeffH via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Dec 2017 23:43:55 +0000
- To: public-webauthn@w3.org
@gmandyam: this issue is related to issue #626. The specification of [#sctn-simple-txauth-extension](https://w3c.github.io/webauthn/#sctn-simple-txauth-extension)'s input value of "A single JSON string prompt" is likely going to change to be something more explicit e.g.: ``` txAuthSimpleArg = ( tstr ) ``` I disagree that we we should make [#sctn-simple-txauth-extension](https://w3c.github.io/webauthn/#sctn-simple-txauth-extension)'s input value be encoded as a CBOR map in the same fashion as [#sctn-generic-txauth-extension](https://w3c.github.io/webauthn/#sctn-generic-txauth-extension)'s args. > > @emlun: What do you mean? Doesn't the quoted passage say that the client extension input does have to be a JSON (-encodable) value? > @gmandyam: No it does not. The quoted passage says "can be encoded in JSON", which is not the same as "have to be JSON-encodable". IMHO the above-cited "can be encoded in JSON" language in section [9.3. Extending request parameters](https://w3c.github.io/webauthn/#sctn-extension-request-parameters) is a bug and ought to be more clearly specified. -- GitHub Notification of comment by equalsJeffH Please view or discuss this issue at https://github.com/w3c/webauthn/issues/725#issuecomment-352139120 using your GitHub account
Received on Friday, 15 December 2017 23:43:58 UTC