Skip to content

Deployment Backend Not Configured

URI: https://docs.ankatech.co/errors/deployment-backend-not-configured
HTTP Status: 409 Conflict

When you see this

A deployment key-protection backend operation was requested and there is no descriptor for it to act on. The three-step surface is configuration, then credential, then activate; supplying a credential or activating before coordinates have been recorded is refused. Nothing was sealed and no envelope row was written — a sealed value with no descriptor to own it is a secret nothing references, nothing evicts and nothing deletes.

Common Causes

  • PATCH /api/v3/admin/platform/setup/backend/credential was called before PUT /api/v3/admin/platform/setup/backend/configuration recorded the backend's coordinates.
  • POST /api/v3/admin/platform/setup/backend/activate was called on a descriptor that carries no sealed credential.

Response Example

{
  "type": "https://docs.ankatech.co/errors/deployment-backend-not-configured",
  "title": "Deployment Backend Not Configured",
  "status": 409,
  "detail": "No deployment key-protection backend is configured. Record the backend's coordinates before supplying its credential.",
  "instance": "/api/v3/admin/platform/setup/backend/credential",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "7e5c9014-2b6d-4a83-91f0-c48d5e7b2a63"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.

How to Resolve

  1. Record the backend's coordinates first with PUT /api/v3/admin/platform/setup/backend/configuration.
  2. Then supply the credential with PATCH /api/v3/admin/platform/setup/backend/credential.
  3. Then activate with POST /api/v3/admin/platform/setup/backend/activate. The body carries no reason and no selfTest member because nothing was contacted, so there is nothing in your cloud account to investigate.

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