The latest versions of the FIDO Alliance specifications are available below. If you are new to FIDO, we recommend you first review the Specifications Overview before proceeding further.
Older versions of the specifications can be found in the specification archive along with the Chinese translation of the UAF 1.0 specifications. The FIDO Specification Status and Intellectual Property Rights (IPR) of the FIDO Alliance specifications can be found here.
The FIDO Alliances publishes the following technical specifications for any implementer to download. In addition, the Alliance is providing support for implementers of FIDO authentication technology by operating the [email protected] public discussion list. Please post any questions you may have about implementing the FIDO specifications in that forum.
The FIDO Alliance produces PDF-formatted specifications as a convenience for readers, however readers are advised to refer to the HTML-formatted specs if they encounter any formatting issues with the PDF-formatted specs. IF YOU ARE NOT YET A MEMBER OF THE FIDO ALLIANCE, AND YOU WOULD LIKE TO COMMENT ON OUR PUBLIC DRAFT SPECIFICATIONS, PLEASE USE THE CONTACT US FORM.
PLEASE NOTE that the FIDO2 Specifications were submitted to the W3C on November 12, 2015 for formal standardization. These are provided here for historic reference only. Implementers are encouraged to work with the W3C WebAuthn specification.
This is a zip file containing the DRAFT specifications public snapshot of FIDO2 also known as W3C WebAuthn, published on September 4, 2015 and delivered to W3C on November 12, 2015. The W3C WebAuthn specification supersedes these documents.
This DRAFT document describes the attestation formats that will be created by FIDO2 authenticators and delivered to FIDO2 servers. The W3C WebAuthn specification supersedes this document.
This DRAFT document contains the signature formats that will be created by FIDO2 authenticators and delivered to FIDO2 servers. The W3C WebAuthn specification supersedes this document.
This Proposed Standard document describes the Client-to-Authenticator Protocol (CTAP) which uses USB, NFC, and / or BLE for communication between browsers or platforms and FIDO2 authenticators.
This overview document describes the various protocol design considerations in detail and also describes the user flows in detail. It describes the layering and intention of each of the detailed protocol documents.
You should read this document first if you are new to UAF.
This overview document describes the various design considerations which go into the protocol in detail and describes the user flows in detail. It describes the layering and intention of each of the detailed protocol documents. It describes the various privacy considerations in the protocol design through the document and summarizes these at the end.
You should read this document first if you are new to U2F.
This document defines the message formats and processing rules for all UAF protocol messages.
This document describes the client side API in the web browser for accessing U2F capabilities. An online service or website can levearge U2F by using this API on the client side and pairing it with a server which can verify U2F messages on the server side. (Later specifications will describe APIs in non-browser contexts).
UAF Application API and Transport Binding Specification This document describes the client side APIs and interoperability profile for client applications to utilize FIDO UAF.
This document describes the binary format of request messages which go from the FIDO U2F server to the FIDO U2F token and the binary format of the response messages from the token to the server. These messages are encoded by the browser (FIDO client) for communication over a particular transport (such as USB) to the cryptographic core of the token which performs key generation and signing. A header file with standard values is also specified.
This document defines Authenticator-specific Modules and the API provided to the FIDO client by ASMs.
This document describes Low-level functionality that UAF Authenticators should implement to support the UAF protocol.
1.2 Review Draft: HTML | PDF FIDO U2F Bluetooth® protocol This document describes the communication protocol between a FIDO client and FIDO authenticators over Bluetooth technology and Bluetooth Smart.
This document describes how to use Elliptic Curve (EC) Direct Anonymous Attestation (DAA) as a form of secure and private attestation for authenticators.
This document describes the communication protocol between a FIDO client and FIDO authenticators over Near Field Communication (NFC).
This standard describes one way relying parties may learn which transports an authenticator supports, by allowing authenticator vendors to embed hardware features as an optional extension in the authenticator's attestation certificate.
This document defines the authenticator metadata. This metadata in turn describes FIDO authenticator form factors, characteristics, and capabilities. The metadata is used to inform relying party interactions with, and make policy decisions about, the authenticators.
This document describes implementation considerations and recommendations for creators of U2F devices and for relying parties implementing U2F support.
Baseline method for relying parties to obtain FIDO Metadata statements.
This document defines the scope of user credentials and how a trusted computing base which supports application isolation may make access control decisions about which keys can be used by which applications and web origins.
This document defines all the strings and constants reserved by UAF protocols.
Provides an analysis of FIDO security based on detailed analysis of security threats pertinent to the FIDO protocols based on its goals, assumptions, and inherent security measures.
This document defines all the strings and constants common to all FIDO specifications.
Defines the technical terms and phrases used in FIDO Alliance specifications and documents.
This is a README for the U2F 1.2 Implementation Draft public snapshot of the Universal Second Factor (U2F) specs as of July 11, 2017.
This is a README for the fido-uaf-README-v1.1-rd-2016100 REVIEW DRAFT public snapshot of in-progress FIDO Alliance Universal Authentication Framework (UAF) specs as approved October 5th, 2016.
This errata is being published to address certain issues that have been identified in the UAF v1.1 Specification. All Specifications and errata are required to be approved by the FIDO Board prior to publication.
Explanation of IPR Status FIDO Alliance specifications progress through various stages, Pre-Draft, Working Draft, Review Draft, Implementation Draft, Proposed Standard and Proposed Standard Expanded to the World. The Promise, the covenant FIDO Alliance Member organizations make not to assert their patent rights against other compliant implementations, is applied differently based on the specification stage. The Promise does not apply for Pre-Draft, Working Draft and Review Draft specification stages. At Implementation Draft stage, the Promise is provided by FIDO Alliance Working Group members to other FIDO Alliance Working Group members. At Proposed Standard stage, the Promise is provided by all FIDO Alliance members to all other FIDO Alliance members. At Proposed Standard Expanded to the World stage, the Promise is provided by all FIDO Alliance members to any party in the world. It is understood that the above is a brief summary and that the actual terms are provided in the FIDO Alliance Membership Agreement, which should be consulted for any specific case.
Patent Notices The FIDO Alliance Membership Agreement provides Members the opportunity to make withdrawals of Granted Claims from the Promise under certain conditions. The FIDO Alliance Membership Agreement should be consulted for the specific conditions. The Board is pleased to report to the public that it has received no such notice pertaining to any of the Specifications published on this site. Implementers interested in learning more about what this means are encouraged to review our IPR Summary and/or section 6 of the FIDO Alliance Membership Agreement.