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

[webauthn] Clearly define the way how RP handles the extensions (#1258)

From: Ki-Eun Shin via GitHub <sysbot+gh@w3.org>
Date: Fri, 12 Jul 2019 09:46:06 +0000
To: public-webauthn@w3.org
Message-ID: <issues.opened-467322556-1562924765-sysbot+gh@w3.org>
Kieun has just created a new issue for https://github.com/w3c/webauthn:

== Clearly define the way how RP handles the extensions ==
WebAuthn defines the list of the extensions. Some of extensions are client extensions and some are authenticator extensions.
In the viewpoint of RP, RP may set list of extensions during create or get ceremony and expect to get the extension outputs by calling `getClientExtensionResults()` or decode extension within the authData.
In case of client only extensions, RP surely needs to get client extension result by calling the defined function.
But for the authenticator extensions, it is not clear which parts should be looked into by RP side.

Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1258 using your GitHub account
Received on Friday, 12 July 2019 09:46:08 UTC

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