Skip to content

Cryptographic Actor Not Found

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

When you see this

The cryptographic actor named in the route does not exist in this tenant, so there is nothing to bind an external subject to.

The actor is never created here, not on a miss and not for convenience. An actor created by the call that binds an external identity to it would exist with whatever defaults the binding path chose, rather than the roles, capability grants and exchange context an administrator decided — and it would have been created by the external identity being bound to it. The actor row count is unchanged after this refusal.

Common Causes

  • The actor identifier is mistyped, or the actor was deleted.
  • The actor belongs to a different tenant than the one in the path.
  • The actor was never provisioned, and the binding request was expected to create it.

Response Example

{
  "type": "https://docs.ankatech.co/errors/bindable-actor-not-found",
  "title": "Cryptographic Actor Not Found",
  "status": 404,
  "detail": "No cryptographic actor 5a83f0d6-91c7-4b2e-8f60-3d17ae924cb8 exists here. An actor is never created by a binding: it would exist with defaults this call chose rather than the roles, grants and exchange context an administrator decided, and it would have been created by the external identity being bound to it. Provision the actor first.",
  "instance": "/api/v3/admin/tenants/3f9a1b62-5d47-4c8e-b0a2-91d7e4f60cc5/workload-identity/actors/5a83f0d6-91c7-4b2e-8f60-3d17ae924cb8/issuer-bindings",
  "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. Provision the cryptographic actor first, with the roles, capability grants and exchange context it should have.
  2. Take the actor identifier from the create response, or from the tenant's actor list.
  3. Re-issue the binding request against the provisioned actor.

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