Skip to content

Trusted Issuer Not Found

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

When you see this

No trusted-issuer declaration with that identifier is reachable from the tenant the request is scoped to.

This is also the answer when the identifier belongs to another tenant. The two responses are byte-identical on purpose: answering 403 for a row that exists and 404 for one that does not would turn the endpoint into an existence oracle that enumerates which authorization servers other customers trust, one probe at a time.

Common Causes

  • The issuer identifier is mistyped, or belongs to a declaration that was already withdrawn.
  • The identifier belongs to a different tenant, or to the deployment plane when a tenant-plane route was called (or the reverse).
  • The declaration was withdrawn between reading the list and issuing this request.

Response Example

{
  "type": "https://docs.ankatech.co/errors/trusted-issuer-not-found",
  "title": "Trusted Issuer Not Found",
  "status": 404,
  "detail": "No trusted issuer 9e2f77a1-3c04-42db-8f5b-1a6d0e93bb41 exists here.",
  "instance": "/api/v3/admin/tenants/3f9a1b62-5d47-4c8e-b0a2-91d7e4f60cc5/workload-identity/issuers/9e2f77a1-3c04-42db-8f5b-1a6d0e93bb41",
  "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 trusted issuers for this tenant and take the identifier from the response rather than from an earlier copy.
  2. Confirm you are calling the right plane: a deployment-wide declaration is not addressable through a tenant route.
  3. Confirm the tenant in the path is the tenant that holds the declaration.

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