Client to Authenticator Protocol (CTAP/CTAP2)

CTAP Authentication Process - Secret Double Octopus

Client To Authenticator Protocol (CTAP) is a specification describing how an application (i.e. browser) and operating system establish communications with a compliant authentication device over USB, NFC or BLE communication mediums.

The specification is part of the FIDO2 project and W3C WebAuthN specification. The specification refers to two CTAP protocol versions.

CTAP1 is the new name for FIDO U2F. It defines how to establish communications between FIDO2-enabled browsers and operating systems and a FIDO U2F device, to enable a second-factor authentication experience.

CTAP2 defines how to establish communication between FIDO2-enabled browsers and operating systems and external authenticators (FIDO Security Keys, mobile devices) to enable a passwordless, second-factor or multi-factor authentication experience.

The general flow of communications defined by CTAP is as follows:

  1. Application (i.e. browser) establishes a connection with the authenticator.
  2. Application gets information about the authenticator and its capabilities.
  3. Application sends a command for an operation that the authenticator supports.
  4. Authenticator replies with response data or error.
Frequently Asked Questions
What is CTAP FIDO?

Client To Authenticator Protocol (CTAP) is a specification describing how an application (i.e. browser) and operating system establish communications with a compliant authentication device over USB, NFC or BLE.

The specification is part of the FIDO2 project and W3C WebAuthN specification.It refers to two CTAP protocol versions.

CTAP1 is the new name for FIDO U2F. It defines how to establish communications between FIDO2-enabled browsers and operating systems and a FIDO U2F device, to enable a second-factor authentication experience.

 

What is CTAP2?

CTAP2 defines how to establish communication between FIDO2-enabled browsers and operating systems and external authenticators (FIDO Security Keys, mobile devices) to enable a passwordless, second-factor or multi-factor authentication experience.

What is the difference between CTAP and CTAP2?

CTAP1 is the new name for FIDO U2F. It defines how to establish communications between FIDO2-enabled browsers and operating systems and a FIDO U2F device, to enable a second-factor authentication experience.

CTAP2 defines how to establish communication between FIDO2-enabled browsers and operating systems and external authenticators (FIDO Security Keys, mobile devices) to enable a passwordless, second-factor or multi-factor authentication experience.