Verify and persist a passkey for the current member
POST/api/v1/auth/passkeys/registration/member/finish
Requires the same recent ordinary session and an exact same-origin proof for cookie requests. It consumes the one-use ceremony, verifies its member and session binding, and atomically persists the credential subject to username, freshness, and passkey-capacity checks.
Request
Responses
- 200
- 400
- 401
- 403
- 409
- 421
- 503
Passkey enrolled
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The request syntax, headers, body, or validated input is malformed or invalid
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The opaque credential is absent, ambiguous, malformed, expired, revoked, or invalid
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The browser mutation did not originate from this application, or the authenticated member lacks the required permission
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The request conflicts with the current resource, revision, lease, credential, or idempotency state
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The request authority or direct peer is outside the configured Jiandu ingress boundary
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
A required core dependency is unavailable; retry with bounded backoff
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.