Delete outdated note about checking registration UV with PRF extension

w3c · Aug 23, 2023 · 7b877b6 · 7b877b6
1 parent bd68fbf
commit 7b877b6
Showing 1 changed file with 0 additions and 2 deletions.
diff --git a/index.bs b/index.bs
@@ -6779,8 +6779,6 @@ Note: this extension may be implemented for [=authenticators=] that do not use [
        1. Set {{AuthenticationExtensionsPRFOutputs/enabled}} to the value of `hmac-secret` in the authenticator extensions output. If not present, set {{AuthenticationExtensionsPRFOutputs/enabled}} to [FALSE].
        1. Set {{AuthenticationExtensionsPRFOutputs/results}} to the decrypted PRF result(s), if any.
 
-Note: If PRF results are obtained during [=registration=] then the [=[RP]=] MUST inspect the [=UV=] bit in the [=flags=] of the response in order to determine the correct value of {{PublicKeyCredentialRequestOptions/userVerification}} for future [=assertions=]. Otherwise results from [=assertions=] may be inconsistent with those from the [=registration=].
-
 : Client extension processing ([=authentication extension|authentication=])
 ::
       1. If {{AuthenticationExtensionsPRFInputs/evalByCredential}} is not empty but {{PublicKeyCredentialRequestOptions/allowCredentials}} is empty, return a {{DOMException}} whose name is “{{NotSupportedError}}”.