Create a copy of this page as a sibling and fill in that copy as instructed below.

Describe platform

To ensure a successful test of the authenticator, please follow these steps:

• Prepare the authenticator that you wish to test. It is recommended to use it only for this test to avoid any conflicts. If necessary, delete the passkey and reset the authenticator's settings (e.g., disable PIN, unregister fingerprint).
  • it may be a hardware authenticator, such as a YubiKey
  • it may be an operating system authenticator, such as Touch ID or Windows Hello
  • it may be a software authenticator, such as tpm-fido
  • it may be a password manager with passkey support, such as Dashlane
• Fill in details about the authenticator in the table below (vendor, model, OS, browser)

• Be prepared to capture screenshots of each system/browser dialogue that appears. (Later in this process, you will register a passkey multiple times)

Capture the platform or browser passkey options

• If there are any options or settings related to "passkeys", "security keys" or similar in your OS/device/... settings, make screenshots and attach them here. If there are any options or settings related to "passkeys", "security keys" or similar in your OS/device/... settings, make screenhots and attach them here.
  
  • If there are password manager options, only capture them
  • If there are browser options, only capture them
  • If there are browser options, only capture them

This is an exemplary path, screenshot only the screen(s) with passkey options (the last one below)

Get diagnostics

• Open https://webauthntest.identitystandards.io/
• Click the "..." button

Set repeated settings

• Click the "+" button to create a passkey. Choose the following values:
  • RP Info: This domain
  • User Info: Bob
  • Attachment: undefined
  • Require Resident Key: true
  • Resident Key (L2): required

It should look like this:

Create passkeys using various settings

If you encounter an error message like "Authenticator data cannot be parsed", it indicates that the combination of arguments used is not supported by the authenticator being tested.

Test User Verification

• Select User Verification: Discouraged and click CREATE.
• I think we should request screenshots at only one creation test, you choose where. Probably not here but in the next creation!!!
  

• Copy-paste the result from the web app

• Select User Verification: Required and click CREATE.

• Copy-paste the result from the web app

• Should this remain? User Verification: Required

AND SO ON

Test Attestation

• Select Attestation: Enterprise and click CREATE.
  
  1. Copy-paste the resulting registration data into row 3. Attestation: Enterprise, or input "unsupported" if there was an error.
• Select Attestation: Direct and click CREATE.
  1. Copy-paste the resulting registration data into row 4. Attestation: Direct, or input "unsupported" if there was an error.
• Select Attestation: Indirect and click CREATE.
  1. Copy-paste the resulting registration data into row 5. Attestation: Indirect, or input "unsupported" if there was an error.
• Select Attestation: None and click CREATE.
  1. Copy-paste the resulting registration data into row 6. Attestation: None, or input "unsupported" if there was an error.
• If none of the previous four tries worked, select Attestation: Undefined and click CREATE.
  
  1. Copy-paste the resulting registration data into row 6. Attestation: None, or input "unsupported" if there was an error.
• If Attestation: Direct worked, select it; otherwise if Attestation: Indirect worked, select it; otherwise select Attestation: Undefined

Test CredProtect Extension

• Select CredProtect Extension: userVerificationOptional and click CREATE.
  
  1. Copy-paste the resulting registration data into row 7. CredProtect Extension: userVerificationOptional, or input "unsupported" if there was an error.
• Select CredProtect Extension: userVerificationOptionalWithCredentialIDList and click CREATE.
  
  1. Copy-paste the resulting registration data into row 8. CredProtect Extension: userVerificationOptionalWithCredentialIDList, or input "unsupported" if there was an error.
• Select CredProtect Extension: userVerificationRequired and click CREATE.
  
  1. Copy-paste the resulting registration data into row 9. CredProtect Extension: userVerificationRequired, or input "unsupported" if there was an error.
• If none of the previous three tries worked, select CredProtect Extension: Undefined and click CREATE.
  
  1. Copy-paste the resulting registration data into row 7. CredProtect Extension: userVerificationOptional, or input "unsupported" if there was an error.
• Select CredProtect Extension: Undefined (if not selected already)

Test cryptography

• Unchecking all following checkboxes: Use ES256, Use ES384, Use ES512, Use RS256, Use EdDSA
• Check Use ES256 and click CREATE.
  
  1. Copy-paste the resulting registration data into row 10. ES256, or input "unsupported" if there was an error.
  2. What about Use ES256? Clear?
     
• Check Use ES384 and click CREATE.
  
  1. Copy-paste the resulting registration data into row 11. ES384, or input "unsupported" if there was an error.
• Check Use ES512 and click CREATE.
  
  1. Copy-paste the resulting registration data into row 12. ES512, or input "unsupported" if there was an error.
• Check Use RS256 and click CREATE.
  
  1. Copy-paste the resulting registration data into row 13. RS256, or input "unsupported" if there was an error.
• Check Use EdDSA and click CREATE.
  
  1. Copy-paste the resulting registration data into row 14. EdDSA, or input "unsupported" if there was an error.

I would skip this and, if needed, place some identifying labels above for easier extraction from test results pages

The results will be aggregated into the summarised table below.