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

Re: [webauthn] Add keyStorage enum to ScopedCredentialOptions

From: gmandyam via GitHub <sysbot+gh@w3.org>
Date: Wed, 01 Mar 2017 19:04:06 +0000
To: public-webauthn@w3.org
Message-ID: <issue_comment.created-283436463-1488395045-sysbot+gh@w3.org>

Will there be provisions in the PR for non-roaming authenticators to 
ignore a keyStorage option where "server" is specified?  Or would the 
makeCredential() fail if the authenticator cannot export key meaterial
 to the RP?

Also, "client" as an option is misleading.  "Client" is Webauthn is 
defined as "Conforming User Agent" - not the same as authenticator (in
 fact it is clearly distinct).

GitHub Notification of comment by gmandyam
Please view or discuss this issue at 
using your GitHub account
Received on Wednesday, 1 March 2017 19:04:13 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 07:26:24 UTC