Skip to content

Passkey Registration Refused

URI: https://docs.ankatech.co/errors/passkey-registration-refused
HTTP Status: 400 Bad Request

When you see this

The response of a passkey registration ceremony (registerPasskey, or the passkey-registration action of the console sign-in) did not verify. Nothing was stored.

The detail is one fixed sentence whatever check failed: which one refused the response is recorded in the service log, never answered, so the answer does not tell a caller which part of a forged response to repair.

Common Causes

  • The registration was made for another origin or another Relying Party ID, for example from a page served on a different host than the console.
  • The challenge was not issued for this person and this session, has expired (5 minutes), or was already used by an earlier attempt.
  • The authenticator did not perform user verification (no PIN, biometric or screen lock).
  • The credential is already registered.
  • The response is malformed.

Response Example

{
  "type": "https://docs.ankatech.co/errors/passkey-registration-refused",
  "title": "Passkey Registration Refused",
  "status": 400,
  "detail": "The passkey registration could not be verified; start a new registration.",
  "instance": "/api/v3/auth/account/authenticators/passkeys",
  "timestamp": 1730000000
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. This is an Auth API body, so it carries no correlation member: correlate through the X-Correlation-Id response header. See Error Index & Overview.

How to Resolve

  1. Start a new registration: request new creation options, then complete the ceremony with them in the same session, within five minutes.
  2. Use the console on its own host name, and confirm the authenticator asks for a PIN, biometric or screen lock.
  3. If the authenticator already holds a passkey for this account, use that passkey instead.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.