Omit tokenBinding in ClientData if not supported.
https://github.com/w3c/webauthn/issues/907 notes that there are three status values for tokenBinding in webauthn, including "not-supported", but that tokenBinding itself is optional. Rather than having two ways to indicate that it's not supported, we're going to eliminate the "not-supported" status and represent that by omitting the value. This matches with Firefox's behaviour. Spec change in https://github.com/w3c/webauthn/pull/914. Change-Id: If47bd218d61dc71eeddab3cc0d22da953b4cc370 Reviewed-on: https://chromium-review.googlesource.com/1062188Reviewed-by:Balazs Engedy <engedy@chromium.org> Commit-Queue: Adam Langley <agl@chromium.org> Cr-Commit-Position: refs/heads/master@{#561592}
Showing
Please register or sign in to comment