Skip to content

Commit

Permalink
Add Google documents
Browse files Browse the repository at this point in the history
  • Loading branch information
agektmr committed Dec 19, 2024
1 parent 963a664 commit 1e28d5b
Show file tree
Hide file tree
Showing 5 changed files with 77 additions and 1 deletion.
3 changes: 2 additions & 1 deletion content/docs/demos-examples/demos.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: "Demo Sites & Services"
description: "Sites and services to demo passkeys"
lead: "Sites and services to demo passkeys"
date: 2023-09-19T16:45:00.148Z
date: 2024-06-25T16:45:00.148Z
draft: false
images: []
menu:
Expand All @@ -24,3 +24,4 @@ These demo sites have been created and are maintained by FIDO2/WebAuthn vendors
- [passkeys.guru (Descope)](https://passkeys.guru/)
- [passkey.org (Yubico)](https://passkey.org)
- [패스키 체험 (SK Telecom)](https://www.passkey-sktelecom.com/experience)
- [try-webauthn.appspot.com (Google)](https://try-webauthn.appspot.com/)
9 changes: 9 additions & 0 deletions content/docs/guides/_index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
---
title: "Guides"
description: "Guides for passkeys developers"
lead: ""
date: 2024-06-25T16:08:00+09:00
draft: false
images: []
weight: 400
---
17 changes: 17 additions & 0 deletions content/docs/guides/codelabs.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
title: "Codelabs"
description: "Passkeys developer codelabs"
date: 2024-06-25T16:09:38.358Z
draft: false
images: []
menu:
docs:
parent: "guides"
weight: 2001
toc: true
---

## Codelabs

* <a href="https://developers.google.com/codelabs/passkey-form-autofill" target="_blank"><button type="button" class="btn btn-light">Implement passkeys with form autofill in a web app {{< icon-external-link size=24 >}}</i></button></a>
* <a href="https://codelabs.developers.google.com/credential-manager-api-for-android" target="_blank"><button type="button" class="btn btn-light">Implement passkeys using Credential Manager API in your Android app {{< icon-external-link size=24 >}}</i></button></a>
33 changes: 33 additions & 0 deletions content/docs/guides/developer-guides.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
---
title: "Developer guides"
description: "Passkeys developer guides"
date: 2024-06-25T16:09:38.358Z
draft: false
images: []
menu:
docs:
parent: "guides"
weight: 1001
toc: true
---

## Server side guides

* <a href="https://developers.google.com/identity/passkeys/developer-guides/server-introduction" target="_blank"><button type="button" class="btn btn-light">Introduction to server-side passkey implementation {{< icon-external-link size=24 >}}</i></button></a>
* <a href="https://developers.google.com/identity/passkeys/developer-guides/server-registration" target="_blank"><button type="button" class="btn btn-light">Server-side passkey registration {{< icon-external-link size=24 >}}</i></button></a>
* <a href="https://developers.google.com/identity/passkeys/developer-guides/server-authentication" target="_blank"><button type="button" class="btn btn-light">Server-side passkey authentication {{< icon-external-link size=24 >}}</i></button></a>

## iOS/iPadOS

* <a href="https://developer.apple.com/documentation/authenticationservices/supporting-passkeys" target="_blank"><button type="button" class="btn btn-light">Supporting passkeys {{< icon-external-link size=24 >}}</i></button></a>

## Android

* <a href="https://developer.android.com/identity/sign-in/credential-manager" target="_blank"><button type="button" class="btn btn-light">Sign in your user with Credential Manager {{< icon-external-link size=24 >}}</i></button></a>

## Deep dives

* <a href="https://web.dev/articles/webauthn-user-verification" target="_blank"><button type="button" class="btn btn-light">User verification deep dive {{< icon-external-link size=24 >}}</i></button></a>
* <a href="https://web.dev/articles/webauthn-discoverable-credentials" target="_blank"><button type="button" class="btn btn-light">Discoverable credentials deep dive {{< icon-external-link size=24 >}}</i></button></a>
* <a href="https://web.dev/articles/webauthn-exclude-credentials" target="_blank"><button type="button" class="btn btn-light">Prevent creation of a new passkey if one already exists {{< icon-external-link size=24 >}}</i></button></a>
* <a href="https://web.dev/articles/webauthn-aaguid" target="_blank"><button type="button" class="btn btn-light">Determine the passkey provider with AAGUID {{< icon-external-link size=24 >}}</i></button></a>
16 changes: 16 additions & 0 deletions content/docs/reference/terms/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,14 @@ A user whose account has [2FA](#2-factor-authentication-2fa) turned on, i.e., wh
This refers to a contract between a user and a [Relying Party (RP)](#relying-party-rp) where the RP must collect at least two distinct authentication factors from the user during a [bootstrap](#account-bootstrapping) sign-in.

## Authenticator Attestation Globally Unique Identifier (AAGUID)

AAGUID is a unique number that identifies the model of the authenticator (not the specific instance of the authenticator). AAGUID can be found as part of a public key credential's authenticator data. RPs can use AAGUID to identify the [passkey provider](#passkey-provider).

<a href="https://web.dev/articles/webauthn-aaguid" target="_blank"><button type="button" class="btn btn-light">web.dev {{< icon-external-link size=24 >}}</button></a>

<a href="https://w3c.github.io/webauthn/#aaguid" target="_blank"><button type="button" class="btn btn-light">WebAuthn Spec Reference {{< icon-external-link size=24 >}}</button></a>

## Account bootstrapping

A [Relying Party (RP)](#relying-party-rp) authenticates a user without any prior knowledge of who the user is. This means that the RP not only has to verify the identity of the user (checking the password, verifying cryptographic signatures, etc), it also has to establish the identity of the user (figure out the user id, username, etc. of the user who’s signing in). This may happen when a user signs into an existing account for the first time on a newly-purchased device; or when a user logs into a website for the first time in a given browser instance. Or when a user logs into a website in a private browsing session. Or when a user signs into a mobile app for the first time on a given device (contrast this with [reauthentication](#reauthentication) below).
Expand Down Expand Up @@ -50,6 +58,8 @@ A generic example of an autofill UI for passkeys is shown below:

The technical name for this feature in the WebAuthn and Credential Management specifications is "Conditional Mediation".

<a href="https://web.dev/articles/passkey-form-autofill" target="_blank"><button type="button" class="btn btn-light">web.dev {{< icon-external-link size=24 >}}</button></a>

<a href="https://w3c.github.io/webauthn/#dom-publickeycredential-isconditionalmediationavailable" target="_blank"><button type="button" class="btn btn-light">WebAuthn Spec Reference {{< icon-external-link size=24 >}}</button></a>

<a href="https://w3c.github.io/webappsec-credential-management/#mediation-requirements" target="_blank"><button type="button" class="btn btn-light">Credential Management Spec Reference {{< icon-external-link size=24 >}}</button></a>
Expand Down Expand Up @@ -86,6 +96,8 @@ A Discoverable Credential (known in previous version of WebAuthn as a "resident

[Passkeys](#passkey) are Discoverable Credentials.

<a href="https://web.dev/articles/webauthn-discoverable-credentials" target="_blank"><button type="button" class="btn btn-light">web.dev {{< icon-external-link size=24 >}}</button></a>

<a href="https://www.w3.org/TR/webauthn-2/#discoverable-credential" target="_blank"><button type="button" class="btn btn-light">Spec Reference {{< icon-external-link size=24 >}}</button></a>

## First-Party Passkey Provider
Expand Down Expand Up @@ -178,12 +190,16 @@ A [Passkey Provider](#passkey-provider) that plugs in to the OS via platform API

A test of User Presence (UP) is used to ensure the user is in local proximity to the authenticator during an authentication or credential creation ceremony. UP is often satisfied by pressing a button or metallic area of a security key, or interacting with a platform authenticator on a device.

<a href="https://web.dev/articles/webauthn-user-verification" target="_blank"><button type="button" class="btn btn-light">web.dev {{< icon-external-link size=24 >}}</i></button></a>

<a href="https://www.w3.org/TR/webauthn-2/#test-of-user-presence" target="_blank"><button type="button" class="btn btn-light">Spec Reference {{< icon-external-link size=24 >}}</button></a>

## User Verification (UV)

User Verification (UV) requires the user to either perform a biometric gesture, enter the device PIN, or enter the device password for the authenticator to authorize creation and/or use of the credential.

<a href="https://web.dev/articles/webauthn-user-verification" target="_blank"><button type="button" class="btn btn-light">web.dev {{< icon-external-link size=24 >}}</i></button></a>

<a href="https://www.w3.org/TR/webauthn-2/#user-verification" target="_blank"><button type="button" class="btn btn-light">Spec Reference {{< icon-external-link size=24 >}}</button></a>

## User-Verifying Roaming Authenticator
Expand Down

0 comments on commit 1e28d5b

Please sign in to comment.