Understand passkey sync across devices via iCloud Keychain and Google Password Manager

domain: w3.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. When a passkey is registered with residentKey=required on an Apple device, iOS/macOS stores it in iCloud Keychain; it is automatically synced to other devices signed in with the same Apple ID under the same iCloud Keychain access group.
  2. On Android, passkeys registered via the Credential Manager API are stored in Google Password Manager and synced across Android devices signed in with the same Google Account.
  3. The credentialBackedUp flag (bit 3 of authenticatorData flags byte) indicates the passkey is synced/backed up; credentialSourceType is discoverable-credential.
  4. From a relying party perspective, synced passkeys behave identically to device-bound passkeys — the same credential ID and public key work on all synced devices; no special server-side handling is needed.
  5. To distinguish synced from hardware-bound credentials, check the credentialBackedUp flag during registration and store it; use this metadata to apply risk policy (e.g. high-value operations may require hardware-bound credentials).

Known gotchas

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans