...
- 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). Sounds scary. What i I already have something on it, or had some UV method set?
- 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 the details in the table below:
$$Tester: | test line 1 test line 2 |
|---|---|
| $$Date: Use '//' wiki date | test line 1 test line 2 |
| $$Authenticator (or device) vendor: Yubico, Apple, Dell, HP, Android phone brand... | |
| $$Authenticator (or device) model: YubiKey 5, iPhone 13, PC model name, MacBook year size, MacBook Air year size, MacBook Pro year size... | test |
| $$OS and its version: iOS 13, macOS 10.5.8, Windows 10 22h2, Windows 11 22h2, Android 13... | test |
| $$Browser and its version: Chrome 114, Firefox 114... | test |
| $$I registered a PIN/password/finger/face in the authenticator before the session: (I guess that should be set for the entire session! Should there be 2 sessions per device? I also guess that phones require some form of screen lock. Perhaps require both options only for security keys?) Enter yes or no$$ | test line 1 test line 2 test line 3 |
- $$Be prepared to capture screenshots of each system/browser dialogue that appears. (Later in this process, you will register a passkey multiple times)
...
Copy-paste the diagnostic results on the right as text (rows are labeled the same, but you may have different values): Platform authenticator (isUVPAA) Available Conditional Mediation (Autofill UI) Not defined CTAP2 support (Firefox) Supported $$ | test line 1 test line 2 test line 3 |
|---|
...