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.ĬTAP 2.1 Proposed Standard with Errata: HTML | PDFĪn API for accessing Public Key Credentials 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. 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. Please post any questions you may have about implementing the FIDO specifications in that forum. In addition, the Alliance is providing support for implementers of FIDO authentication technology by operating the public discussion list. The FIDO Alliances publishes the following technical specifications for any implementer to download. The FIDO Specification Status and Intellectual Property Rights (IPR) of the FIDO Alliance specifications can be found here. ![]() Older versions of the specifications can be found in the specification archive along with the Chinese translation of the UAF 1.0 specifications. These requirements are covered in the Authenticator Certification program found on the Certified Authenticator Levels page. ![]() In addition to meeting the technical requirements, the FIDO Alliance developed further security requirements that need to be implemented to enhance the security assurance of each device. If you are new to FIDO, we recommend you first review the Specifications Overview before proceeding further. The latest versions of the FIDO Alliance user authentication specifications are available below.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |