Re: [webauthn] txAuthSimple does not conform to extension requirements

>>Another option is to make the description of txAuthSimple more like txAuthGeneric (, where the client extension input is provided as a CBOR Map, with the corresponding key/value pairs.

>What would be the benefit of this?

Avoiding an unnecessary casting between JSON and CBOR (which is not a huge concern), and consistency between txAuthSimple and txAuthGeneric.

>What do you mean? Doesn't the quoted passage say that the client extension input does have to be a JSON (-encodable) value?

No it does not.  The quoted passage says "can be encoded in JSON", which is not the same as "have to be JSON-encodable".  

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

Received on Tuesday, 12 December 2017 21:14:10 UTC