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

Describe the platform

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

• For this test, you need a computer or mobile device and a hardware or software authenticator. It may be:
  
  • Hardware authenticator, such as a YubiKey.
  • Operating system authenticator, such as Touch ID or Windows Hello.
  • Software authenticator, such as tpm-fido.
  • Password manager with passkey support, such as Dashlane.
• The actions performed during this test are parts of regular usage and should not affect it in any way. However, you may decide to use a brand-new authenticator, reset or clear it to avoid any conflicts during the test.
• If necessary, delete the passkey that you create during this testing if it prevents you from creating it again. This should not happen, but if it does, please provide a screenshot and an accompanying note. If you are willing to, reset the authenticator's settings (e.g., disable PIN, unregister fingerprint).
• Then don't test it, or fill "yes" into "I registered a PIN/password/finger/face in the authenticator before the session".
• Fill in the details in the table below:

}}

• 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/spaceship settings (related to the authenticator you are going to use), capture screenshots and paste or attach them here.
  
  • If there are password manager options, only capture them.
  • If there are browser options, capture them instead.
  • If there are operating system options, capture them instead.

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

Please paste screenshots in or outside this table as suitable:

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

• Capture and paste below the screenshot of various prompts, screens, dialogues, questions or messages that show up during passkey registration as you encounter them.
  • If some options are offered, snapshot them as well, but do not change anything.
  • Capture screenshots in each step of the first passkey creation.
  • Also, capture screenshots when new screens appear during subsequent passkey creations and add them here.
  • There is no need to repeat similar screenshots. Usually, interactions will look mostly the same, so try not to duplicate screenshots of the same steps.

  • 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.

  • You can also add a text note to a screenshot if encounter an error or find something interesting.

Please insert or paste screenshots in or outside this table as suitable:

Test User Verification

• Select User Verification: Discouraged and click CREATE.
• Follow the requested steps to create a passkey, then copy-paste the result from the web app.

}}

• Select User Verification: Required and click CREATE.
• Follow the requested steps to create a passkey, then copy-paste the result from the web app.

}}

Test Attestation

• Select Attestation: Enterprise and click CREATE.
• Follow the requested steps to create a passkey, then copy-paste the result from the web app.

}}

• Select Attestation: Direct and click CREATE.
• Follow the requested steps to create a passkey, then copy-paste the result from the web app.

}}

• Select Attestation: Indirect and click CREATE.
• Follow the requested steps to create a passkey, then copy-paste the result from the web app.

}}

• Select Attestation: None and click CREATE.
• Follow the requested steps to create a passkey, then copy-paste the result from the web app.

}}

• If none of the previous four tries worked,
  • Select Attestation: Undefined and click CREATE.
  • Follow the requested steps to create a passkey, then copy-paste the result from the web app.

}}

• 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

• Uncheck all the 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.
     
• Uncheck UseES256, 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.
• Uncheck UseES384, 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.
• Uncheck UseES512, 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.
• Uncheck UseRS256, 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.