key_binding_challenge: The key-binding JWT does not answer a live challenge
The SD-JWT's key-binding JWT verifies, but it does not answer a live challenge of this deployment: its nonce was never issued for this account, was already used, or has expired (challenges last 300 seconds and are single-use); or its aud is not this deployment; or its iat is more than 300 seconds old. Nothing was linked and the challenge, if live, is still unused.
For a client pinned at Dynamo-Version 1.7.0 or later, a presentation of a credential already linked to this account never reaches this check: it answers 409 conflict first (at 1.7.0 the identical presentation, at 1.8.0 or later the same credential with any key-binding JWT). A client pinned earlier, or a single-tenant request that sends no Dynamo-Version, skips that check and can meet this code.
What to do
- Fetch a new challenge (
POST /owner/v1/link-challenges) for the same account. - Sign a fresh KB-JWT with its
nonceandaudandiatnow, and link within 300 seconds.
On the wire
HTTP 400, error type invalid_request_error. Every client gets errorDetail, with or without Dynamo-Error-Detail: 1. A client pinned before Dynamo-Version 1.8.0 (on a single-tenant core, also one that names no version) gets the earlier doc_url form: the docs base followed by /errors/key_binding_challenge.md (with the default docs base, a doubled errors/errors/ path); on the multi-tenant hosted tier a request that names no version is served the account's default (1.8.0 for new accounts).
{
"error": "key_binding_challenge",
"errorDetail": {
"type": "invalid_request_error",
"code": "key_binding_challenge",
"message": "the key-binding nonce is not a live challenge for this account (unknown, used or expired)",
"param": "sdJwt",
"doc_url": "…/errors/key_binding_challenge.md",
"fix": "fetch a new challenge and sign a fresh KB-JWT with its nonce and aud within 300 s"
}
}
See all error codes.