密碼金鑰會透過密碼管理工具建立、儲存，並在裝置間同步。舉例來說，在 Android 版 Chrome 的網站上建立的密碼金鑰，預設會儲存在 Google 密碼管理工具中，然後同步至可使用 Google 密碼管理工具的不同環境，例如 macOS、Windows、Linux 和 ChromeOS 上的 Chrome。使用者可以根據環境選擇要將密碼金鑰儲存在哪個密碼管理工具，或從哪個密碼管理工具驗證密碼金鑰。在使用者傳回憑證之前，RP (依賴方) 無法得知使用者的密碼管理工具。
Google 密碼管理工具
Google 密碼管理工具會在 Android 和 Chrome 上儲存、提供及同步密碼金鑰。Google 密碼管理工具預設會在 Android 上啟用密碼金鑰提供者功能，並可供所有應用程式使用，包括 Chrome 和其他瀏覽器。電腦作業系統 (Windows、macOS、Linux 和 ChromeOS) 上的 Chrome 也支援 Google 密碼管理工具。
使用者透過 Google 密碼管理工具建立密碼金鑰後，系統會同步處理並進行端對端加密。如果是在電腦上建立 Google 密碼管理工具的第一個密碼金鑰，Chrome 會要求建立 Google 密碼管理工具 PIN 碼，並使用該 PIN 碼。使用者必須登入 Google 帳戶，並輸入 Android 裝置螢幕鎖定密碼或 Google 密碼管理工具 PIN 碼，才能在新環境中解密已同步的密碼金鑰。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-04-15 (世界標準時間)。"],[[["\u003cp\u003ePasskeys are synchronized across devices using a password manager like Google Password Manager or iCloud Keychain.\u003c/p\u003e\n"],["\u003cp\u003eChrome supports passkeys on Android, iOS, macOS, Windows, Linux, and ChromeOS, with platform-specific storage options.\u003c/p\u003e\n"],["\u003cp\u003eAndroid users can choose their preferred passkey provider in System Settings on Android 14 or higher.\u003c/p\u003e\n"],["\u003cp\u003eCross-device authentication allows users to sign in with a passkey stored on a different device using a QR code.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Password Manager is the default passkey provider for Chrome on most platforms and encrypts synced passkeys end-to-end.\u003c/p\u003e\n"]]],[],null,["# Passkey support on Android and Chrome\n\nPasskeys are created on, saved to, and synchronized across devices through a\npassword manager. For example, passkeys created on a website on Chrome on\nAndroid are stored to the Google Password Manager by default, and then\nsynchronized to different environments where Google Password Manager is\navailable, such as Chrome on macOS, Windows, Linux and ChromeOS. The user can\nchoose which password manager to store a passkey to or to authenticate a passkey\nfrom depending on the environment. The user's password manager is opaque to the\nRP (relying party) until a credential is returned.\n\nGoogle Password Manager\n-----------------------\n\nGoogle Password Manager stores, serves and synchronizes passkeys on Android and\nChrome. Google Password Manager is enabled by default as a passkey provider on\nAndroid and available for all apps including Chrome and other browsers. Chrome\non desktop operating systems (Windows, macOS, Linux and ChromeOS) comes with\nGoogle Password Manager support as well.\n\nWhen a user creates a passkey with Google Password Manager, it's synchronized\nand end-to-end encrypted. If the first passkey for Google Password Manager is\ncreated on desktop, Chrome asks to create a Google Password Manager PIN and it\nwill be used. The user needs to sign in to their Google Account and enter their\nAndroid device screen lock or Google Password Manager PIN to decrypt a synced\npasskey on a new environment.\n**Figure 1**: A dialog displayed when Chrome asks for a Google Password Manager PIN.\n\nPasskey support on Android\n--------------------------\n\n### Credential Manager\n\nAndroid apps support passkeys through [the Credential\nManager](https://developer.android.com/identity/sign-in/credential-manager)\n[Jetpack](https://developer.android.com/jetpack) library. Credential Manager\nhandles different credential types such as passkeys, passwords and identity\nfederation. Passkeys are supported on devices that run Android 9 (API level 28)\nor higher. Passwords and Sign in with Google are supported starting with Android\n4.4.\n\nOn many devices, Credential Manager stores passkeys to Google Password Manager\nby default. Users can choose other password managers as its passkey providers in\nthe System Settings on Android 14 or higher.\n**Figure 2**: Users can choose a passkey provider in Android System Settings.\n\nThe user can choose to sign in using a passkey stored on another device. For\nexample, when a passkey is stored on an iPhone and the user is trying to sign in\non an Android app that doesn't have a passkey on it, the user can choose to \"use\na different phone or tablet\" to show a QR code on the Android device, then scan\nit using the iPhone and authenticate cross-device.\n**Figure 3**: QR code dialog is displayed for a cross-device passkey sign-in.\n\nPasskey support on Chrome\n-------------------------\n\nChrome on Android, macOS, Windows, Linux and ChromeOS stores and authenticate\nwith passkeys on Google Password Manager by default. Chrome on iOS or iPadOS can\nstore and authenticate with passkeys on Google Password Manager by enabling it\nin the System Settings.\n**Figure 4**: Touch ID based passkey sign-in on Chrome on macOS.\n\nChrome on all platforms supports cross-device authentication. To use a passkey\nfrom your Android or iOS device, select the appropriate option when asked. To\nlearn more about cross-device authentication user experience, read [Sign-in with\na phone](/identity/passkeys/use-cases#sign-in-with-a-phone). \n\n| | Android | iOS/iPadOS | macOS | Windows | Linux | ChromeOS |\n|-----------------------------|---------|------------|-------|---------|-------|----------|\n| Google Password Manager | | ^1^ | | | | |\n| Cross-device authentication | | | | | | |\n[Supported,\n^1^ Requires iOS/iPadOS 17 or higher]\n\n### Android\n\nChrome on Android OS 9 or higher supports passkeys. Passkeys created in Chrome\non Android are stored in the Google Password Manager. Google Password Manager\nsyncs passkeys and makes them available on other platforms as well.\n\nOn Android 14 or higher, passkeys on Chrome on Android can be created and stored\nin any password manager that's selected in the System Settings as a passkeys\nprovider.\n| **Note:** This may not be reflected on some Android OEM devices.\n\n### iOS / iPadOS\n\nChrome on iOS/iPadOS 16 or higher support passkeys. Passkeys created on\niOS/iPadOS are stored to the iCloud Keychain or the Password app by default.\nUsers on iOS/iPadOS 17 or higher can set Chrome as an autofill provider in the\nSystem Settings to store passkeys to the Google Password Manager.\n\n### macOS\n\nChrome on macOS supports passkeys. Passkeys created in Chrome on macOS can be\nstored in the Google Password Manager or in iCloud Keychain (macOS 13.5 or\nhigher). Passkeys in iCloud Keychain are synchronized across the user's Apple\ndevices and can be used by other browsers and apps.\n\nChrome on macOS can also store passkeys on Chrome profile if the user chooses\nto, which aren't synchronized to other environments.\n\n### Windows\n\nChrome on Windows supports passkeys. Passkeys created in Chrome on Windows are\nstored in the Google Password Manager.\n\n### Linux\n\nChrome on Linux supports passkeys. Passkeys created in Chrome on Linux are\nstored in the Google Password Manager.\n\n### ChromeOS\n\nChrome on ChromeOS supports passkeys. Passkeys created in Chrome on ChromeOS\nare stored in the Google Password Manager."]]
