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

[webauthn] clarify "authenticator model": RPs may perform feature-based authenticator selection

From: =JeffH via GitHub <sysbot+gh@w3.org>
Date: Fri, 13 Oct 2017 21:30:01 +0000
To: public-webauthn@w3.org
Message-ID: <issues.opened-265424167-1507930186-sysbot+gh@w3.org>
equalsJeffH has just created a new issue for https://github.com/w3c/webauthn:

== clarify "authenticator model": RPs may perform feature-based authenticator selection ==
clarify "authenticator model": RPs may perform feature-based authenticator selection with both 
1. [`navigator.credentials.create()`](https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-create) (which invokes [webauthn's #createCredential](https://w3c.github.io/webauthn/#createCredential)), and 
2. [`navigator.credentials.get()`](https://w3c.github.io/webappsec-credential-management/#dom-credentialscontainer-get) (which invokes [webauthn's #getAssertion](https://w3c.github.io/webauthn/#getAssertion)).

In (1), options stipulating "require resident key" and "require user verification" are expected to be passed (see also #536, #524), e.g., ultimately to [CTAP's authenticatorMakeCredential command](https://fidoalliance.org/specs/fido-v2.0-rd-20170927/fido-client-to-authenticator-protocol-v2.0-rd-20170927.html#authenticatorMakeCredential).

In (2), options stipulating "require user verification", "require user presence test"  are expected to be passed (see also #629, #524), e.g., ultimately to [CTAP's authenticatorGetAssertion command](https://fidoalliance.org/specs/fido-v2.0-rd-20170927/fido-client-to-authenticator-protocol-v2.0-rd-20170927.html#authenticatorGetAssertion).

Please view or discuss this issue at https://github.com/w3c/webauthn/issues/645 using your GitHub account
Received on Friday, 13 October 2017 21:29:50 UTC

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