This is the Level 1 attestation mode checker. It's a work-in-progress. Code is on GitHub, and deploys automatically on merge to main.

You can open this page inside an iframe for testing as well, or open a cross-origin iframe (which is prohibited and will give an error).

You can also load this page on port 8443 to test that alternate ports work for a given RP ID.

This page works in Firefox 74, Chrome or Edge 91, or Safari 14.1 and later.

Using an NFC reader on Linux

Linux browsers can't use USB NFC readers, so tapping a key does nothing. To test one anyway, use a bridge that makes the reader look like a USB key:

  1. Install and start your distro's pcscd and CCID driver packages.
  2. If pcscd doesn't see your reader (common with PN533 readers like the ACR122U), blacklist the pn533_usb kernel module and reboot.
  3. Run fido2-hid-bridge as root and leave it running.
  4. In the Advanced box at the bottom of the page, set "Authenticator hint" to "Security key" so the browser asks for the key straight away.
  5. Click Create Credential and hold the key on the reader until the result appears.


  

  

Advanced

Relying Party ID to use. "bin.coffee" and "webauthn.bin.coffee" should be the only valid options. Ports, paths, schema and such should be forbidden.

Attestation type.

Authenticator attachment. (Platform authenticators are built into the device, like Windows Hello, Touch ID or a built-in fingerprint reader. Cross-platform authenticators are roaming, like USB, NFC or BLE security keys, or a phone.)

Authenticator hint, sent with both Create and Get. (WebAuthn Level 3 hints tell the browser which kind of authenticator to offer first. "Security key" goes straight to a USB key, including an NFC key behind a bridge. Browsers that don't support hints ignore it.)

FIDO AppID to use. (If set, Get Assertion will send it with the AppID compatibility extension. "https://bin.coffee/AppId" and "https://webauthn.bin.coffee/" are valid options for Firefox. Only "https://webauthn.bin.coffee/" is valid for Chrome.)

Should this page aggressively loop forever on an operation? (Test denial-of-service to WebAuthn)