From 63b8da959312b908c0dc39400e96ebec96296219 Mon Sep 17 00:00:00 2001 From: jakani24 Date: Thu, 4 Apr 2024 20:24:03 +0200 Subject: [PATCH] Update user.html --- src/server/cyberhex-code/test/user.html | 441 +++++++++++++++++++++--- 1 file changed, 385 insertions(+), 56 deletions(-) diff --git a/src/server/cyberhex-code/test/user.html b/src/server/cyberhex-code/test/user.html index c1cec00..eb4970b 100644 --- a/src/server/cyberhex-code/test/user.html +++ b/src/server/cyberhex-code/test/user.html @@ -1,36 +1,45 @@ - - - - - - lbuchs/WebAuthn Test - - - - -

lbuchs/WebAuthn

-
- - - -
- - + + + + + +

lbuchs/WebAuthn

+
A simple PHP WebAuthn (FIDO2) server library.
+
+
+
 
+
 
+
Simple working demo for the lbuchs/WebAuthn library.
+
+
 
+ + + + + + + +
+ + + + + +
+
 
+ +
+ + +
+ +
 
+
Relying Party
+

A valid domain string that identifies the + WebAuthn Relying Party
on whose behalf a given registration or authentication ceremony is being performed.

+
+ + +
+ +
 
+
User
+
+ + + You get the user ID back when checking registration (as userHandle), if you're using client-side discoverable credentials. + You can identify with this ID the user who wants to login. + A user handle is an opaque byte sequence with a maximum size of 64 bytes, and is not meant to be displayed to the user. + The user handle MUST NOT contain personally identifying information about the user, such as a username or e-mail address. +
+
+ + + only for display, i.e., aiding the user in determining the difference between user accounts with similar display names. +
+
+ + + A human-palatable name for the user account, intended only for display. +
+ +
 
+
user verification
+
+ + +
+ +
+ + +
+ +
+ + +
+ +
 
+
type of authenticator
+
+ + +
+
+ + +
+
+ + +
+
+ + +
+
+ + +
+ +
 
+
attestation
+
+ + +
+
+ + +
+ +
 
+
attestation statement format
+
+ + +
+ +
+ + +
+ +
+ + +
+ +
+ + +
+ +
+ + +
+ +
+ + +
+ +
+ + +
+ + +
 
+
attestation root certificates
+ +
+ + +
+ +
+ + +
+ +
+ + +
+ +
+ + +
+ +
+ + +
+ +
+ + +
+ +
+ + +
+ +
(Nothing checked = accept all)
+
 
+ +
+ +
+ +
 
+
If you select a root ca, direct attestation is required to validate your client with the root.
+ The browser may warn you that he will provide informations about your device.
+ When not checking against any root ca (deselect all certificates), + the client may change the assertion from the authenticator (for instance, using an anonymization CA),
+ the browser may not warn about providing informations about your device. +
+
+ Copyright © 2023 Lukas Buchs - license therms +
+ +
+
+
+

Here you can see what's saved on the server:

+ +
+
+