WebAuthn 2 - Revision history

Tom: /* CTAP 2.2 */

2025-03-28T04:57:03Z

‎CTAP 2.2

Tom: /* CTAP 2.2 */

2025-03-28T04:54:29Z

‎CTAP 2.2

Tom: /* References */

2024-10-10T18:20:13Z

‎References

Tom: /* CTAP 2.1 */

2024-04-22T18:35:27Z

‎CTAP 2.1

Tom: /* CTAP 2.1 */

2021-11-19T05:02:03Z

‎CTAP 2.1

Tom: /* CTAP 2.1 */

2021-11-19T05:01:36Z

‎CTAP 2.1

Tom: /* CTAP 2.1 */

2021-11-19T05:00:06Z

‎CTAP 2.1

Tom: /* Context */

2021-11-09T17:24:55Z

‎Context

Tom: /* Context */

2021-11-09T17:08:48Z

‎Context

Tom: /* Context */

2021-11-09T16:52:46Z

‎Context

@@ Line 24: / Line 24: @@
 ===CTAP 2.2===
 * 2025-03 [https://self-issued.info/?p=2631 Third Version of FIDO2 Client to Authenticator Protocol (CTAP 2.2) Now a Standard]
-* In final draft 2024-04 https://fidoalliance.org/specifications/download/
+* 2024-04 [https://fidoalliance.org/specifications/download/ In final draft]
 ===Cross-Origin iFrame Support===

@@ Line 23: / Line 23: @@
 This is currently just targeted at Chrome, the discussion is [https://groups.google.com/a/chromium.org/g/blink-dev/c/Vfg2o0peyYg/m/KCLBo9yHAQAJ?pli=1 here].
 ===CTAP 2.2===
 * In final draft 2024-04 https://fidoalliance.org/specifications/download/

← Older revision		Revision as of 18:20, 10 October 2024
Line 75:		Line 75:
	[[Category: Authentication]]		[[Category: Authentication]]
	[[Category: Profile]]		[[Category: Profile]]
		+	[[Category: Web]]

← Older revision		Revision as of 18:35, 22 April 2024
Line 22:		Line 22:

	This is currently just targeted at Chrome, the discussion is [https://groups.google.com/a/chromium.org/g/blink-dev/c/Vfg2o0peyYg/m/KCLBo9yHAQAJ?pli=1 here].		This is currently just targeted at Chrome, the discussion is [https://groups.google.com/a/chromium.org/g/blink-dev/c/Vfg2o0peyYg/m/KCLBo9yHAQAJ?pli=1 here].
		+	===CTAP 2.2===
		+	* In final draft 2024-04 https://fidoalliance.org/specifications/download/

	===Cross-Origin iFrame Support===		===Cross-Origin iFrame Support===

@@ Line 15: / Line 15: @@
 CTAP is a standard that allows a client application to communicate with a security key such as Google Titan or YubiKey over USB, near field communication (NFC), or [[Bluetooth]]. CTAP is a low level standard which is typically implemented at either the operating system or the browser level and engaged using a FIDO2 client.
-In addition, Enterprise Attestation features two approaches at the CTAP 2.1 layer - Vendor Facilitated EA and Platform Managed EA. Technically CTAP 2.1 is a security key extension that is designed to store a hash value (the BLOB) that can be used to authenticate externally provided data.
+Enterprise Attestation features two approaches at the CTAP 2.1 layer - Vendor Facilitated EA and Platform Managed EA. Technically CTAP 2.1 is a security key extension that is designed to store a hash value (the BLOB) that can be used to authenticate externally provided data.
 Vendor-Facilitated EA - Customers and authenticator vendors collaborate on configuring EA with the customer’s RP IDs. The authenticators are for the customer’s exclusive use, and the configured authenticators only return EA when requested by the RP IDs.

@@ Line 13: / Line 13: @@
 ===CTAP 2.1===
-CTAP is a standard that allows a client application to communicate with a security key such as Google Titan or YubiKey over USB, near field communication (NFC), and Bluetooth. CTAP is a low level standard which is typically implemented at either the operating system or the browser level and engaged using a FIDO2 client.
+CTAP is a standard that allows a client application to communicate with a security key such as Google Titan or YubiKey over USB, near field communication (NFC), or [[Bluetooth]]. CTAP is a low level standard which is typically implemented at either the operating system or the browser level and engaged using a FIDO2 client.
 In addition, Enterprise Attestation features two approaches at the CTAP 2.1 layer - Vendor Facilitated EA and Platform Managed EA. Technically CTAP 2.1 is a security key extension that is designed to store a hash value (the BLOB) that can be used to authenticate externally provided data.

← Older revision		Revision as of 05:00, 19 November 2021
Line 13:		Line 13:

	===CTAP 2.1===		===CTAP 2.1===
		+	CTAP is a standard that allows a client application to communicate with a security key such as Google Titan or YubiKey over USB, near field communication (NFC), and Bluetooth. CTAP is a low level standard which is typically implemented at either the operating system or the browser level and engaged using a FIDO2 client.
		+
	In addition, Enterprise Attestation features two approaches at the CTAP 2.1 layer - Vendor Facilitated EA and Platform Managed EA. Technically CTAP 2.1 is a security key extension that is designed to store a hash value (the BLOB) that can be used to authenticate externally provided data.		In addition, Enterprise Attestation features two approaches at the CTAP 2.1 layer - Vendor Facilitated EA and Platform Managed EA. Technically CTAP 2.1 is a security key extension that is designed to store a hash value (the BLOB) that can be used to authenticate externally provided data.

@@ Line 3: / Line 3: @@
 ==Context==
-* [[WebAuthn 2]] is near completion and should be issued as a W3C  spec early in 2021. The W3C distinguishes their spec versions “Levels”, and as such the new specification released in early 2021 will be labeled Level 2 (L2)
+* [[WebAuthn 2]] is near completion and should be issued as a W3C spec early in 2021. The W3C distinguishes their spec versions “Levels”, and as such the new specification released in early 2021 will be labeled Level 2 (L2).
-.*[[WebAuthn 3] is the next versions.
+* [[WebAuthn 3]] is the next version.
-===Enterprise Attestation:===
+===Enterprise Attestation===
-Enterprise Attestation (EA) is focused on device management within an enterprise, a familiar endeavor for any company. Enterprise Attestation is standardized in WebAuthn and FIDO CTAP2 and permits a relying party to request uniquely identifying information from authenticators during a registration event. These function was designed for controlled deployments within an enterprise where the organization wishes to tie registrations to specific authenticators, allowing management functions such as tracking key distribution and usage.
+Enterprise Attestation (EA) is focused on device management within an enterprise, a familiar endeavor for any company. Enterprise Attestation is standardized in WebAuthn and FIDO CTAP2 and permits a relying party to request uniquely identifying information from authenticators during a registration event. This function was designed for controlled deployments within an enterprise where the organization wishes to tie registrations to specific authenticators, allowing management functions such as tracking key distribution and usage.
 Usage tracking features supported with Enterprise Attestation do run counter to WebAuthn’s privacy principles on traceability. To address this concern, authenticators which support Enterprise Attestation are not available to consumers. Authenticator vendors must pre-load these attestations, with corporate management policies controlling if an site or service can request such an attestation. In short, only authenticators programmed with unique attestation by an organization can have their usage tracked on the same organization’s sites.