Tenant Name Confirmation Required
URI: https://docs.ankatech.co/errors/custody-move-confirmation-required
HTTP Status: 422 Unprocessable Content
When you see this
A key custody move back to the deployment's key protection backend was asked for without the tenant's name typed exactly in confirmTenantName. Nothing was written.
On a private-cloud or on-premise deployment, a tenant on its own key management service can move back to the backend it inherits from the deployment. That move takes the tenant's keys out of the key management service its organisation controls, so it is confirmed the way the console confirms every irreversible custody decision: by typing the tenant's name.
Response Example
{
"type": "https://docs.ankatech.co/errors/custody-move-confirmation-required",
"title": "Tenant Name Confirmation Required",
"status": 422,
"detail": "A move back to the deployment's key protection backend requires the tenant's name, typed exactly, to confirm it. Nothing was written.",
"instance": "/api/v3/admin/platform/tenants/8f14e45f-ceea-467a-9575-0d5b2a1f3c11/key-custody/moves",
"timestamp": 1793696400,
"extensions": {
"requestId": "9c41e7a2-5b08-4d3f-a6e1-2f7c90b4d815"
}
}
Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.
How to Resolve
Send the request again with the tenant's name, exactly as the tenant record holds it:
For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.