FIDO Alliance

Passkey Central

Authenticate Conference

Interoperability Testing

Interoperability Testing is a required step in the certification process.

The following types of Interoperability Testing are supported for certification:

Interoperability Testing Events

Interoperability Testing events are a forum for implementers to gather and validate that their implementations are compatible with each other. It is also a functional requirement for server and authenticator product certifications. 

All testing is completed remotely. Given the testing environment, participants that are completing testing for an authenticator should be prepared to set up both web camera viewing and screen sharing capability so that the interoperability steps can be visually verified as they are performed, including all actions being performed on all devices.  

Each implementer will test their implementation with those of other implementers. For example, a FIDO2 Server will test with all FIDO2 Authenticators present at an event; likewise, a UAF Client/Authenticator will test with all UAF Servers. For each combination of participants, the corresponding UAF and FIDO2 testing procedures listed below will be performed. Implementations showing that they can pass the testing procedures with all the other implementations at the event, or that can show that any failed testing procedures are not due to their implementations being non-conformant with the FIDO specifications, will pass the interoperability event and remain eligible for proceeding to the next certification step.

Prior to registering for an interoperability event, an implementation must pass conformance testing self‐validation and the implementation must not be changed before the interoperability event. Participants must register at least 12 days prior to the event.

Implementers are strongly advised to participate in pre-testing. Pre-testing is scheduled to take place the week prior to each event. The intent of pre-testing is to give the companies that will be participating in the interoperability event the ability to exchange software, metadata, and test with each other ahead of the event. For those implementers that opt-in to pre-testing, their contact information will be shared with other implementers ahead of the event so that they may communicate with each other to share the appropriate information and perform pre-testing.

In the event that there are not enough implementations to hold an interoperability testing event, the event will be canceled and potential participants will be notified 10 days before the event. These events are held at least once every 90 days for active versions of the specifications, this includes all versions that have not yet reached a sunset date. A schedule of all upcoming events can be found below.

Interoperability Events (FIDO2 and FIDO UAF)

FIDO 2024 Interoperability Event Dates:

  • September 16-20, 2024
  • December 2-6, 2024
Register Now

On Demand Testing

On Demand Testing has been introduced as an alternative to attending Interoperability Events. On Demand Testing is available year-round.

On Demand testing uses FIDO® Certified reference implementations to complete testing. An implementation is eligible for On Demand testing if the number of reference implementations is equal to the minimum requirements for testing (three implementations from three unique vendors in each implementation class). Vendors can view the Reference Implementation Library.

FIDO members with certified implementations can donate their implementations to the FIDO Reference Implementation Library by filling out the Donation Form.

There is currently one option available for On Demand Testing:

Virtual

Virtual On Demand Certification requires the vendor submitting for On Demand testing to provide the Certification Secretariat access to, and instructions for, the operation of their implementation. The Certification Secretariat will facilitate the On Demand Interoperability Testing Process. Contact information for a representative from the vendor company must be provided, and the representative must be available during their testing slot if any questions or issues come up during testing.

Vendors interested in Virtual On Demand Testing can register here. Once you have registered, you will be contacted by the Certification Manager to coordinate a time for the On Demand Testing. A non-disclosure agreement is required to protect test participants’ confidential information. The non-disclosure agreement is available here.

Testing Procedures

UAF Interoperability Testing Procedures

Following the policies above, UAF testing will iterate through the prescribed combination of Authenticators / ASMs, Clients and Servers. This will require the following configuration for each set of tests:

  • The Client+Authr combo, or Client and ASM+Authr combo will be loaded on to a single implementation
  • The Server will install the metadata for the Authenticator with corresponding policies and permissions

For each prescribed combination, the following tests will be performed in front of a facilitator:

  1. Register: perform valid registration with the server.
  2. Authenticate: perform valid authentication with the server.
  3. Transaction: perform a transaction with the server. The test must show a text or image indicator of the transaction that is being performed and confirmation that the transaction was successful.
  4. De-Register: remove the registration from the device. Confirm that de-registration was successful by attempting an authentication with the server and confirming that it fails.

Note that due to the time required for configuration of each test and the potential number of combinations for UAF interoperability testing, each test event will span three days. Implementers are expected to attend each day, even if their implementations have already passed all of their designated tests, to facilitate any necessary re-testing. If it is determined that fewer days of testing are required for the interoperability test, participants will be notified at minimum 7 days prior to the event or as soon as reasonably possible.

U2F Interoperability Testing Procedures

Following the policies above, U2F testing will iterate through the prescribed combination of Authenticators and Server. Interoperability testing is performed with the Chrome browser as the U2F Client. Testing is performed with the native U2F functionality of the browser and the U2F Chrome Extension will not be allowed in testing. This policy may be changed when other U2F Clients become available. Each combination of Authenticator and Server will be required to perform the following tests for a facilitator:

  1. Register: The U2F Authenticator will be required to register itself with the U2F Server.
  2. Authenticate: The U2F Authenticator, after being registered with the server, will be required to demonstrate that it can authenticate with the server.

Per the specifications, human interaction is required for each of these steps, such as the touch of a button; the insertion or removal of a device; etc. If the insertion of a device is being used as the form of human interaction, it should require being re-inserted each time a test step is performed.

Implementations may also perform the following test steps:

  1. Negative Register: Register with an invalid certificate in a way that should be rejected by the server.
  2. Negative Authentication: After valid registration, authenticate with invalid credentials in a way that may be rejected by the server.

These optional steps are optional for a client to implement, since some implementations may have difficulty implementing invalid certificates or the other mechanisms required for performing these test steps. However, for clients that do perform these optional steps, servers are required to pass the interoperability testing.

FIDO2 Interoperability Testing Procedures

FIDO2 testing will iterate through the prescribed combination of Authenticators, Browsers, and Servers.

This will require the following configuration for each set of tests:

Required for all Servers and Authenticators

  1. Register: The FIDO2 Authenticator will be required to register itself with the FIDO2 Server.
  2. Authenticate: The FIDO2 Authenticator, after being registered with the server, will be required to demonstrate that it can authenticate with the server.
  3. Reset: erase and revert back to factory settings and reauthenticate

Optional Authenticator Functionality

  1. Client PIN: demonstrate PIN-based user verification (if applicable)
    1. Set PIN
    2. Register with PIN
    3. Authenticate with PIN
    4. Change PIN
    5. Authenticate with new PIN
  2. Resident Key: demonstrate that authenticator can create a resident key (if applicable)
  3. Multi-Account: demonstrate that the authenticator can support multiple users at the same service (if applicable)
  4. HMAC extension

Required Browser Interoperability

  1. Servers
    1. Firefox 61 or later with a reference U2F token
    2. Edge Edge Edge 44.17723.1000.0 with all eligible participating authenticators
    3. Chrome 69 or later with all eligible participating authenticators
  2. Authenticators:
    1. USB CTAP2 Authenticators
      1. Edge Edge Edge 44.17723.1000.0 with all participating servers
      2. Chrome 69 or later with all participating servers
    2. NFC CTAP2 Authenticators
      1. Edge Edge Edge 44.17723.1000.0 with all participating servers
    3. BLE CTAP2 Authenticators
      1. Chrome 69 or later with all participating servers

Level 1 Authenticator Certification is a required component for FIDO Certification. All implementations must complete and pass the testing procedures for Level 1 Authenticator Certification (Section 5.4.4) in order to achieve FIDO Certification.

Per the specifications, human interaction is required for each of these steps, such as the user verification gesture; the insertion or removal of a device; etc. If the insertion of a device is being used as the form of human interaction, it should require being re-inserted each time a test step is performed.

Level 1 Authenticator Certification Testing Procedures

For Authenticators seeking Level 1 Authenticator Certification, Authenticator Security Requirements below in Table 3 must be verified during Conformance Self-Validation or Interoperability Testing. For more information visit the Authenticator Certification Level page.

Requirements and the Vendor Questionnaire are defined in the Authenticator Security Requirements.

Note: Authenticators completing L2 and higher are not required to demonstrate the Requirements during Conformance Self-Validation or Interoperability Testing, the Authenticator Security Requirements are evaluated by an Accredited Security Laboratory during the Security Evaluation step of Authenticator Certification.

Evaluation Methods include Conformance Self-Validation and Interoperability Testing:

  • For Conformance Self-Validation, the Requirement is verified automatically during registration or testing.
  • For Interoperability Testing, the Vendor shall demonstrate to the Test Proctor how the Authenticator meets the Requirement during Interoperability Testing.

L1 Interoperability Requirements Mapping

Specification(s)Authenticator Certification RequirementEvaluation Method
UAF & FIDO21.4Interoperability Testing
UAF & FIDO21.9Interoperability Testing
UAF, U2F, & FIDO23.1Interoperability Testing
UAF & FIDO23.4Interoperability Testing
UAF & FIDO23.5Interoperability Testing
UAF, U2F, & FIDO23.9Interoperability Testing
UAF & FIDO24.4Interoperability Testing
UAF, U2F, & FIDO26.2Interoperability Testing
UAF, U2F, & FIDO26.3Interoperability Testing