Create a copy of this page as a sibling and complete it as instructed below. Please do not disturb markers such as  {10{ and }}.

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 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 the authenticator in any way. However, you may choose 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).
  • Fill in the details in the table below:

Tester:
@ (name yourself){10{

}}Date:
Use '//' to input date{15{

 

}}Authenticator (or device) vendor:
Yubico, Apple, Dell, HP, Android phone brand...{17{
Dashlane
}}Authenticator (or device) model:
YubiKey 5 NFC, iPhone 13, PC model name, MacBook year size, MacBook Air year size, MacBook Pro year size...{20{
Dashlane browser extension for Firefox
}}OS and its version:
iOS 13, macOS 10.5.8, Windows 10 22H2, Windows 11 22H2, Android 13...{25{

Ubuntu 22

}}Browser and its version:
Chrome 114, Firefox 114...{30{
Firefox 117
}}I registered a PIN/password/finger/face in the authenticator before the session:
Yes or No
(
The situation where you have not previously registered in the authenticator is interesting for checking if the passkey creation will trigger user registration.){35{

No

}}

  • 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 you are using a password manager, capture its passkey-related options.
    • If you are using a browser supporting passkeys, capture its options instead.
    • If you are using an operating system to manage passkeys, capture its options instead.

Possible locations:

    • Windows 11: Settings > Accounts > Passkeys
    • iOS: Settings > Apple ID > iCloud > Passwords & Keychain
    • Chrome (Windows): Settings > Autofill and passwords > Password Manager > Manage passkeys

These are exemplary paths. You need to screenshot the only passkey-related options. Please paste screenshots in or outside this table as suitable:





















Get diagnostics

  • Open https://webauthntest.identitystandards.io/.
  • Log in using any user name - this is probably just for the app's internal logging.
  • Click the "..." button.
  • If there are any problems while doing the above, try another time or use another device. If the problem persists, please let us know over Slack.

}}Copy-paste the diagnostic results on the right as text (rows are labelled the same):

Platform authenticator (isUVPAA)


Conditional Mediation (Autofill UI)


CTAP2 support (Firefox)


{40{


Not available

Supported

Supported

}}

Set repeated settings

  • Click the "+" button to create a passkey. Choose the following:
    • 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 at each step of the first passkey creation.
    • Also, capture screenshots when new screens appear during subsequent passkey creations and add them here.
    • Try not to duplicate screenshots of the same steps, as interactions will likely look similar.
    • 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 add a note to a screenshot if you encounter an error or find something interesting.
    • If you are wonderinf wgy

Please insert or paste screenshots in this table as suitable, preferably putting the related screenshots in one row (you can place a note beneath an image in the same cell):

Seq1






Seq2 (just new screens)






Seq3 (just new screens)





Seq4 (just new screens)





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.

Copy-paste the result on the right:
Put Unsupported if there was an error{45{

Credential ID
C64D43D41DB8583434AB7691B7AE8532

RP ID
webauthntest.identitystandards.io

AAGUID
531126D6-E717-415C-9320-3D9AA6981239

Credential Registration Data [more details]
Key Type: EC
Discoverable Credential: true
Attestation Type: none (unverified)
UP=1, UV=0, BE=1, BS=1, AT=1, ED=0, SignCount=0

Last Authentication Data [more details]
No authentications

}}

  • Select User Verification: Required and click CREATE.
  • Follow the requested steps to create a passkey, then copy-paste the result from the web app.
  • Note that the latest result is the rightmost in the bottom row. You may delete already pasted results.
  • All authenticators should be able to register multiple passkeys for the same domain, so you do not need to delete the previously created one. It is likely that the passkeys you create will override each other since they are for the same domain and use the same user name "bob@example.com").

Copy-paste the result on the right:
Put Unsupported if there was an error{50{

Credential ID
0E95ACAEE1928D47EE8837773FDDDBA9

RP ID
webauthntest.identitystandards.io

AAGUID
531126D6-E717-415C-9320-3D9AA6981239

Credential Registration Data [more details]
Key Type: EC
Discoverable Credential: true
Attestation Type: none (unverified)
UP=1, UV=1, BE=1, BS=1, AT=1, ED=0, SignCount=0

Last Authentication Data [more details]
No authentications

}}

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.

Copy-paste the result on the right:
Put Unsupported if there was an error{55{

Credential ID
6AE69B7B02DC1EC65CF2C635FB0F3D20

RP ID
webauthntest.identitystandards.io

AAGUID
531126D6-E717-415C-9320-3D9AA6981239

Credential Registration Data [more details]
Key Type: EC
Discoverable Credential: true
Attestation Type: none (unverified)
UP=1, UV=1, BE=1, BS=1, AT=1, ED=0, SignCount=0

Last Authentication Data [more details]
No authentications

If registration worked, click on "Credential Registration Data [more details]" and copy-paste the content of the dialogue:

Require Resident Key
true

Authenticator Data
UP=1, UV=1, BE=1, BS=1, AT=1, ED=0, SignCount=0

Authenticator Data in Hex
0B997CCCEB3AEB29C55C94A894B11CF01A24B4C8AE706F328CC2EA8CEBC4AD5C5D00000000531126D6E717415C93203D9AA698123900106AE69B7B02DC1EC65CF2C635FB0F3D20A50102032620012158207E5BE0EA75A636D6D50927443691C29DDAA7E66117ECBB2EA8478078FA0046B8225820D64C5023EDA6FF0556EA107B431627C6BAA9F2DFBE5A4464483F7A1ED3E93271

Public Key
EC key: A50102032620012158207E5BE0EA75A636D6D50927443691C29DDAA7E66117ECBB2EA8478078FA0046B8225820D64C5023EDA6FF0556EA107B431627C6BAA9F2DFBE5A4464483F7A1ED3E93271

Extension Data
No extension data

Attestation Statement Chain
none

Attestation Statement in Hex
A0

}}

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

Copy-paste the result on the right:
Put Unsupported if there was an error{60{

Credential ID
7DD47680A6BD8F1EB698B8B85CC5BABD

RP ID
webauthntest.identitystandards.io

AAGUID
531126D6-E717-415C-9320-3D9AA6981239

Credential Registration Data [more details]
Key Type: EC
Discoverable Credential: true
Attestation Type: none (unverified)
UP=1, UV=1, BE=1, BS=1, AT=1, ED=0, SignCount=0

Last Authentication Data [more details]
No authentications

If registration worked, click on "Credential Registration Data [more details]" and copy-paste the content of the dialogue:

Require Resident Key
true

Authenticator Data
UP=1, UV=1, BE=1, BS=1, AT=1, ED=0, SignCount=0

Authenticator Data in Hex
0B997CCCEB3AEB29C55C94A894B11CF01A24B4C8AE706F328CC2EA8CEBC4AD5C5D00000000531126D6E717415C93203D9AA698123900107DD47680A6BD8F1EB698B8B85CC5BABDA50102032620012158207B013C879D2B6DEDC1386047852BA87F5EDA3523A110FB8CD0D7EA312BF48C0B225820D0AC00B0E5282ED3E18363BEA59A3ACDEB0D6CB81ABA8D7225469D258DEBF160

Public Key
EC key: A50102032620012158207B013C879D2B6DEDC1386047852BA87F5EDA3523A110FB8CD0D7EA312BF48C0B225820D0AC00B0E5282ED3E18363BEA59A3ACDEB0D6CB81ABA8D7225469D258DEBF160

Extension Data
No extension data

Attestation Statement Chain
none

Attestation Statement in Hex
A0

}}

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

Copy-paste the result on the right:
Put Unsupported if there was an error{65{

Credential ID
3F6716E5A8445D6BF7405303084B4053

RP ID
webauthntest.identitystandards.io

AAGUID
531126D6-E717-415C-9320-3D9AA6981239

Credential Registration Data [more details]
Key Type: EC
Discoverable Credential: true
Attestation Type: none (unverified)
UP=1, UV=1, BE=1, BS=1, AT=1, ED=0, SignCount=0

Last Authentication Data [more details]
No authentications

If registration worked, click on "Credential Registration Data [more details]" and copy-paste the content of the dialogue:

Require Resident Key
true

Authenticator Data
UP=1, UV=1, BE=1, BS=1, AT=1, ED=0, SignCount=0

Authenticator Data in Hex
0B997CCCEB3AEB29C55C94A894B11CF01A24B4C8AE706F328CC2EA8CEBC4AD5C5D00000000531126D6E717415C93203D9AA698123900103F6716E5A8445D6BF7405303084B4053A5010203262001215820EE7DF9DE10D0E4D7974F9570494B391D782A3A4AED79A1CC7B146F43792BD4AA225820DB8AFEC284EAA72E7DABE4D94DAAA102B35E2E580D826303FBA0F734FB7B397D

Public Key
EC key: A5010203262001215820EE7DF9DE10D0E4D7974F9570494B391D782A3A4AED79A1CC7B146F43792BD4AA225820DB8AFEC284EAA72E7DABE4D94DAAA102B35E2E580D826303FBA0F734FB7B397D

Extension Data
No extension data

Attestation Statement Chain
none

Attestation Statement in Hex
A0

}}

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

Copy-paste the result on the right:
Put Unsupported if there was an error{70{

Credential ID
C45EE45DEBB21D9D6E0A70610699FBB5

RP ID
webauthntest.identitystandards.io

AAGUID
531126D6-E717-415C-9320-3D9AA6981239

Credential Registration Data [more details]
Key Type: EC
Discoverable Credential: true
Attestation Type: none (unverified)
UP=1, UV=1, BE=1, BS=1, AT=1, ED=0, SignCount=0

Last Authentication Data [more details]
No authentications

}}

  • 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.
  • Otherwise, skip this step.

Copy-paste the result on the right:
Put Unsupported if there was an error{75{

(skipped)

}}

  • If Attestation: Direct worked, select it. Otherwise, if Attestation: Indirect worked, select it. Otherwise, select Attestation: Undefined.

Test CredProtect Extension

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

Copy-paste the result on the right:
Put Unsupported if there was an error{80{

Credential ID
757D3A52F4E9AB585A0D3DCCB25377DC

RP ID
webauthntest.identitystandards.io

AAGUID
531126D6-E717-415C-9320-3D9AA6981239

Credential Registration Data [more details]
Key Type: EC
Discoverable Credential: true
Attestation Type: none (unverified)
UP=1, UV=1, BE=1, BS=1, AT=1, ED=0, SignCount=0

Last Authentication Data [more details]
No authentications

}}

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

Copy-paste the result on the right:
Put Unsupported if there was an error{85{

Credential ID
9AEED31A8E1FD1EB1696B35413AA57BF

RP ID
webauthntest.identitystandards.io

AAGUID
531126D6-E717-415C-9320-3D9AA6981239

Credential Registration Data [more details]
Key Type: EC
Discoverable Credential: true
Attestation Type: none (unverified)
UP=1, UV=1, BE=1, BS=1, AT=1, ED=0, SignCount=0

Last Authentication Data [more details]
No authentications

}}

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

Copy-paste the result on the right:
Put Unsupported if there was an error{90{

Credential ID
6208092E953EC3F966599F995BCC13C0

RP ID
webauthntest.identitystandards.io

AAGUID
531126D6-E717-415C-9320-3D9AA6981239

Credential Registration Data [more details]
Key Type: EC
Discoverable Credential: true
Attestation Type: none (unverified)
UP=1, UV=1, BE=1, BS=1, AT=1, ED=0, SignCount=0

Last Authentication Data [more details]
No authentications

}}

  • If none of the previous three tries worked:
    • Select CredProtect Extension: Undefined and click CREATE.
    • Follow the requested steps to create a passkey, then copy-paste the result from the web app.
  • Otherwise, skip this step.

Copy-paste the result on the right:
Put Unsupported if there was an error{95{

(skipped)

}}

  • 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.
  • Follow the requested steps to create a passkey, then copy-paste the result from the web app.

Copy-paste the result on the right:
Put Unsupported if there was an error{100{

Credential ID
B0A6E78EDF6966DA4A2BCC883AC252B2

RP ID
webauthntest.identitystandards.io

AAGUID
531126D6-E717-415C-9320-3D9AA6981239

Credential Registration Data [more details]
Key Type: EC
Discoverable Credential: true
Attestation Type: none (unverified)
UP=1, UV=1, BE=1, BS=1, AT=1, ED=0, SignCount=0

Last Authentication Data [more details]
No authentications

}}

  • Uncheck Use ES256, check Use ES384 and click CREATE.
  • Follow the requested steps to create a passkey, then copy-paste the result from the web app.

Copy-paste the result on the right:
Put Unsupported if there was an error{105{

Unsupported

}}

  • Uncheck Use ES384, check Use ES512 and click CREATE.
  • Follow the requested steps to create a passkey, then copy-paste the result from the web app.

Copy-paste the result on the right:
Put Unsupported if there was an error{110{

Unsupported

}}

  • Uncheck Use ES512, check Use RS256 and click CREATE.
  • Follow the requested steps to create a passkey, then copy-paste the result from the web app.

Copy-paste the result on the right:
Put Unsupported if there was an error{115{

Unsupported

}}

  • Uncheck Use RS256, check Use EdDSA
  • and click CREATE.
  • Follow the requested steps to create a passkey, then copy-paste the result from the web app.

Copy-paste the result on the right:
Put Unsupported if there was an error{120{

Unsupported

}}

Conclusion

Do you have any additional observations or comments related to the entire procedure:{125{

The Dashlane prompt is an iframe included into the page, so while the dialog with the WebAuthn parameters selection is open, the Dashlane prompt cannot be confirmed nor canceled. I had to go into the developer console and close the dialog.

The master password for Dashlane was used as the user verification.

When an unsupported signing algorithm was selected, the Dashlane prompt did not show at all.

}}

  • Please do not forget to paste any pending screenshots in the above tables.
  • You may also paste the screenshot with the passkey(s) created during this test. The list of created passkeys is usually shown along with platform or browser passkey options that you were already asked to screenshot.

Thank you!

  • No labels