From 86083114d01ef80468d85ccb0c43da89afb9b95d Mon Sep 17 00:00:00 2001 From: "J.C. Jones" Date: Wed, 10 Jan 2018 12:21:29 -0700 Subject: [PATCH] Fix #715 - add a conformance class note for FIDO U2F Attesation Types Editorial fix: Note that U2F authenticators can't store-and-return a user handle. --- index.bs | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/index.bs b/index.bs index ce10bb39a..fe64ee388 100644 --- a/index.bs +++ b/index.bs @@ -257,6 +257,11 @@ Agent=]. As described in [[#use-cases]], an authenticator may be implemented in the operating system underlying the User Agent, or in external hardware, or a combination of both. +### Backwards Compatibility with FIDO U2F ### {#conforming-authenticators-u2f} + +[=Authenticators=] that only support the [[#fido-u2f-attestation]] have no mechanism to store a +[=user handle=], so the returned {{AuthenticatorAssertionResponse/userHandle}} will always be null. + ## [RPS] ## {#conforming-relying-parties} A [=[RP]=] MUST behave as described in [[#rp-operations]] to obtain the security benefits offered by this specification.