60388: User display name not provided

This error occurs when you create a Verify Passkeys Factor without the user display name needed for passkey registration. When you create a Passkeys Factor, friendly_name is required, and the returned registration options include publicKey.user.displayName.

• The request body for POST /v2/Services/{ServiceSid}/Passkeys/Factors did not include friendly_name.
• Your application sent an empty or missing value for the field that should populate the passkey user's display name in the registration options.
• Your application used identity as the only user value and did not provide a separate human-readable factor name. identity as an immutable external identifier and friendly_name as the human-readable value for the Factor.

• Include friendly_name and identity in the JSON body when you create the Passkeys Factor. The Passkeys quickstart shows both values in the factor creation request.
• Populate friendly_name with a human-readable value that helps distinguish the Factor. this field as a human-facing name for the Factor and the Passkeys response shows that value in publicKey.user.displayName.
• Keep your user-facing display text separate from identity. Use identity as an immutable identifier and send the human-readable label through friendly_name when you create the Factor.
• Inspect the Factor creation response before you begin browser registration and confirm the returned options.publicKey.user.displayName contains the expected value.

• Verify Passkeys quickstart
• Passkeys Factor resource
• Entity Resource