W3C home > Mailing lists > Public > public-webauthn@w3.org > August 2019

Re: [webauthn] Certain issues in client extension pass-through specification (#1273)

From: Mike Jones via GitHub <sysbot+gh@w3.org>
Date: Wed, 14 Aug 2019 19:51:47 +0000
To: public-webauthn@w3.org
Message-ID: <issue_comment.created-521393208-1565812305-sysbot+gh@w3.org>
As discussed on the 14-Aug-19 working group call, the pass-through transformation is already unambiguously specified.  We understand that one consequence of the way that it is specified is that floating point parameters with whole integer values will be passed as CBOR integers, rather than CBOR floats.  This was an intentional choice, since JavaScript historically has had only one (floating point) representation for numeric values and we certainly wanted interfaces using only integers to be represented using CBOR integers.

Yes, if an authenticator implements an extension using floating point values and it wants it to work in pass-through mode, it must be prepared to accept these values when represented either as CBOR floats or CBOR integers.  While not ideal, this is workable in practice, and well understood.

I believe that this issue should be closed with no action on this basis.

GitHub Notification of comment by selfissued
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1273#issuecomment-521393208 using your GitHub account
Received on Wednesday, 14 August 2019 19:51:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:59:06 UTC