Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21ce0918f2a376a

Jump to content

Client to Authenticator Protocol

From Wikipedia, the free encyclopedia
(Redirected from CTAP2)

The Client to Authenticator Protocol (CTAP) enables a roaming, user-controlled cryptographic authenticator (such as a smartphone or a hardware security key) to interoperate with a client platform such as a laptop. The standard is also adopted as ITU-T Recommendation X.1278.[1][2]

Standard

[edit]

CTAP is complementary to the Web Authentication (WebAuthn) standard published by the World Wide Web Consortium (W3C).[3] WebAuthn and CTAP are the primary outputs of the FIDO2 Project, a joint effort between the FIDO Alliance and the W3C.[4]

CTAP is based upon previous work done by the FIDO Alliance, in particular the Universal 2nd Factor (U2F) authentication standard. Specifically, the FIDO U2F 1.2 Proposed Standard (July 11, 2017) became the starting point for the CTAP Proposed Standard, the latest version 2.2 of which was published on February 28, 2025.[5]

The CTAP specification refers to two protocol versions, the CTAP1/U2F protocol and the CTAP2 protocol.[6] An authenticator that implements CTAP2 is called a FIDO2 authenticator (also called a WebAuthn authenticator). If that authenticator implements CTAP1/U2F as well, it is backward compatible with U2F.

The protocol uses the CBOR binary data serialization format.

References

[edit]
  1. ITU (2018-12-18). "New ITU standards to overcome the security limitations of passwords". ITU News. Archived from the original on 2021-06-28. Retrieved 2021-06-28.
  2. "X.1278: Client to authenticator protocol/Universal 2-factor framework". www.itu.int. Archived from the original on 2021-06-28. Retrieved 2021-06-28.
  3. Balfanz, Dirk; Czeskis, Alexei; Hodges, Jeff; Jones, J.C.; Jones, Michael B.; Kumar, Akshay; Liao, Angelo; Lindemann, Rolf; Lundberg, Emil, eds. (4 March 2019). "Web Authentication: An API for accessing Public Key Credentials Level 1". World Wide Web Consortium (W3C). Archived from the original on 4 March 2019. Retrieved 4 March 2019.
  4. "FIDO2: Moving the World Beyond Passwords". FIDO Alliance. Archived from the original on 22 April 2018. Retrieved 30 January 2019.
  5. "Client to Authenticator Protocol (CTAP)". fidoalliance.org. Archived from the original on 2025-03-28. Retrieved 2025-03-26.
  6. Brand, Christiaan; Czeskis, Alexei; Ehrensvärd, Jakob; Jones, Michael B.; Kumar, Akshay; Lindemann, Rolf; Powers, Adam; Verrept, Johan, eds. (January 30, 2019). "Client to Authenticator Protocol (CTAP)". FIDO Alliance. Archived from the original on 17 March 2022. Retrieved 7 March 2019.
[edit]