Certification Overview

The FIDO Certification program allows members and non-members to measure compliance and ensure interoperability among products and services that support FIDO specifications. Companies completing certification may display the FIDO® Certified logo to demonstrate to consumers, customers and partners that they have created a high‐quality, interoperable FIDO implementation that is known to work with other FIDO implementations. The latest version of the Functional Certification Program Policy documentation is available here, and the review of this document is the recommended starting point.

FIDO-Graphic--v02

Policy Versions:

The following table includes links to the current and previous versions of the Functional Certification Policy.

When the policy document is updated, changes are mandatory for new certifications 90 days after the publication date.

Policy Version Publication Date Mandatory for New Certifications Date
1.2.5 2017-03-10 2017-06-07
1.2.4 2017-02-07 2017-05-08
1.2.3 2016-12-01 2017-03-01
1.2.2 2016-09-08 2016-12-07
1.2.1 2016-07-28 2016-10-26
1.2.0 2016-05-18 2016-08-16
1.1.1 2016-03-17 2016-06-15
1.1.0 2015-09-03 2015-12-02
1.0.0 2014-03-19 2014-06-17

Supported Specification Versions:

Certification is always available for the latest version of a FIDO Specification.

The Certification Availability date is the first day Certification is available, and the Sunset Date is the day that Certification will no longer be available. Sunset dates are assigned when a new version of a specification family is available for Certification. For Servers the period between certification availability of the new version and the sunset date of the previous version is 6 months, and for Clients and Authenticators is 18 months.

Certification is currently supported for the following specification versions:

SPECIFICATION IMPLEMENTATION CLASS VERSION CERTIFICATION AVAILABILITY DATE SUNSET DATE
UAF Server 1.0 2015-04-02
UAF Clients/Authenticators 1.0 2015-04-02
U2F Server 1.0 2015-04-02 2017-06-07
U2F Authenticator 1.0 2015-04-02 2018-06-07
U2F Server 1.1 2016-12-07
U2F Authenticator 1.1 2016-12-07

Steps to FIDO Certification:

  1. Conformance self‐validation, where test tools are used to validate that the implementation conforms to the FIDO specifications.
  2. Interoperability testing, where testing is performed at a proctored event to ensure that implementations are functional and compatible with other implementations.
  3. Certification submission, where all the required documentation is submitted as a request for certification.
  4. Trademark usage (optional). After executing the Trademark License Agreement, implementers may use the FIDO® Certified mark and logo on their product, packaging, and marketing literature.

The certification process is managed by the FIDO Alliance staff. Should you have any questions not answered by the FAQs , please feel free to contact us at
info@fidoalliance.org .