Skip to content

Actor Issuer Binding Not Found

URI: https://docs.ankatech.co/errors/actor-issuer-binding-not-found
HTTP Status: 404 Not Found

When you see this

No actor issuer binding with that identifier is reachable from the tenant the request is scoped to.

The same response is returned for a binding belonging to another tenant and for one belonging to a different actor of the same tenant. All three are byte-identical: distinguishing them would enumerate which workload identities other customers have bound, one probe at a time.

Common Causes

  • The binding identifier is mistyped, or the binding was already removed.
  • The binding belongs to a different actor than the one named in the path.
  • The binding belongs to a different tenant.

Response Example

{
  "type": "https://docs.ankatech.co/errors/actor-issuer-binding-not-found",
  "title": "Actor Issuer Binding Not Found",
  "status": 404,
  "detail": "No actor issuer binding 1d5c9b74-6e30-4a92-a7f1-08c3b5d21e6a exists here.",
  "instance": "/api/v3/admin/tenants/3f9a1b62-5d47-4c8e-b0a2-91d7e4f60cc5/workload-identity/actors/5a83f0d6-91c7-4b2e-8f60-3d17ae924cb8/issuer-bindings/1d5c9b74-6e30-4a92-a7f1-08c3b5d21e6a",
  "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. List the bindings for the actor named in the path and take the identifier from that response.
  2. Confirm the actor identifier in the path owns the binding you mean — a binding of the same tenant under a different actor answers identically.
  3. Confirm the tenant in the path is the tenant that holds the binding.

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