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

[webauthn] AttestationResponse vs AssertionResponse

From: Adam Powers via GitHub <sysbot+gh@w3.org>
Date: Tue, 27 Mar 2018 16:01:31 +0000
To: public-webauthn@w3.org
Message-ID: <issues.opened-309032856-1522166490-sysbot+gh@w3.org>
apowers313 has just created a new issue for https://github.com/w3c/webauthn:

== AttestationResponse vs AssertionResponse ==
There seems to be a weird asymmetry between `AuthenticatorAttestationResponse` and `AuthenticatorAssertionResponse`:

* Attestations return a CBOR map in the `attestationObject`, one of the fields of which is `authenticatorData`.
* Assertions return an object, one of the fields of which is `authenticatorData`.

There is no functional reason to return a CBOR map for attestations and an object for assertions, especially when they are containing similar fields. My understanding is that the APIs are this way because the attestation interface was converted to CBOR (with the argument that "servers need to understand CBOR anyway") but the same editorial conversion never happened for assertions.

Perhaps the only reason to find a solution to this issue is that it impacts the users of the API that may be confused by the two different representations. Also for architectural cleanliness and preventing OCD people from losing their minds...

Please view or discuss this issue at https://github.com/w3c/webauthn/issues/854 using your GitHub account
Received on Tuesday, 27 March 2018 16:01:40 UTC

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