key_binding_required: The SD-JWT link has no key-binding JWT
An sd_jwt identity link must end with a key-binding JWT (KB-JWT) signed by the holder key in the credential's cnf.jwk, over a challenge this deployment issued. This presentation ends without one. Nothing was linked.
At Dynamo-Version 1.8.0 or later, a presentation of a credential already linked to this account never reaches this check: it answers 409 conflict first, with or without a key-binding JWT.
What to do
- Fetch a challenge:
POST /owner/v1/link-challengeswith{"accountId": "acct_…"}. The answer carriesnonce,audandexpiresAt. - Sign a KB-JWT (
typkb+jwt) with the holder key, carrying thatnonceandaud,iatnow, andsd_hashover the presentation; append it after the last~. - Link again 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_required.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_required",
"errorDetail": {
"type": "invalid_request_error",
"code": "key_binding_required",
"message": "sd_jwt links need a key-binding JWT over a challenge from POST /owner/v1/link-challenges (fail closed)",
"param": "sdJwt",
"doc_url": "…/errors/key_binding_required.md",
"fix": "fetch a challenge (POST /owner/v1/link-challenges) and append a KB-JWT signed by the cnf key over it"
}
}
See all error codes.