Skip to content

Workload Credential Conflict

URI: https://docs.ankatech.co/errors/workload-credential-conflict
HTTP Status: 409 Conflict

When you see this

The public key submitted for an administrative workload is already registered: its RFC 7638 thumbprint, which becomes the credential's kid, is unique in the deployment. Nothing was stored.

Common Causes

  • The key was registered on this workload already, or on another workload.
  • A bootstrap request lists the same key twice.
  • A rotation submits the key it is meant to replace.

Response Example

{
  "type": "https://docs.ankatech.co/errors/workload-credential-conflict",
  "title": "Workload Credential Conflict",
  "status": 409,
  "detail": "This public key is already registered. Generate a new key pair and register its public key.",
  "instance": "/api/v3/admin/tenants/7d2f4a10-9c31-4b8e-a5d6-2f11c0b47e93/workloads/9b2f6c1e-3d4a-4c8b-a1e7-5f0d2c9b8a71/credentials",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000"
  }
}

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

How to Resolve

  1. Generate a new key pair for the workload and register its public half.
  2. Never share one key between two workloads: each workload is attributed by the key it signs with.

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