Passkeys use cryptographic key pairs stored on the user’s device. Authentication happens with a biometric check (such as Face ID, Touch ID, or a fingerprint scan) or a local device PIN. This makes passkeys both safer—since they can’t be phished or reused—and easier to use, since users don’t need to remember or type credentials.Documentation Index
Fetch the complete documentation index at: https://docs.dynamic.xyz/docs/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- You need to have the Dynamic Client initialized.
- You need to have the passkey MFA enabled in your environment’s settings in the Dynamic dashboard.
Registering a new passkey
CallingregisterPasskey will prompt the user to register a new passkey in their device and register it in the Dynamic server,
so next time the user can complete an MFA challenge with it or even sign-in with it if enabled in the environment’s settings.
Registering a passkey will automatically authenticate it, so you don’t need to call authenticatePasskeyMFA after registering a passkey.
Doing MFA authentication with a passkey
CallingauthenticatePasskeyMFA will prompt the user to authenticate with a passkey in their device and complete an MFA challenge.
The authentication will be successful if the user authenticates with the passkey in their device and it gets validated in the Dynamic server.
With step-up authentication (recommended)
PassrequestedScopes to receive an elevated access token for sensitive actions:
With MFA token (deprecated)
Deleting a passkey
CallingdeletePasskey will delete a passkey from the Dynamic server.
Getting all registered passkeys for a user
CallinggetPasskeys will return all registered passkeys for the authenticated user.