W3C home > Mailing lists > Public > public-webauthn@w3.org > May 2016

Re: [webauthn] Add opaque data extension

From: =JeffH via GitHub <sysbot+gh@w3.org>
Date: Wed, 25 May 2016 01:28:48 +0000
To: public-webauthn@w3.org
Message-ID: <issue_comment.created-221449654-1464139727-sysbot+gh@w3.org>
Does this last paragraph of the current section 5 
{#extension-request-parameters} address this use case?

For extensions that specify additional authenticator processing only, 
it is desirable that the platform need not know the extension. To 
support this, platforms SHOULD pass the client argument of unknown 
extension as the authenticator argument unchanged, under the same 
extension identifier. The authenticator argument should be the CBOR 
encoding of the client argument, as specified in Section 4.2 of 
[RFC7049]. Clients SHOULD silently drop unknown extensions whose 
client argument cannot be encoded as a CBOR structure.

GitHub Notification of comment by equalsJeffH
Please view or discuss this issue at 
https://github.com/w3c/webauthn/issues/98#issuecomment-221449654 using
 your GitHub account
Received on Wednesday, 25 May 2016 01:28:49 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:38:15 UTC