Skip to content

TSA Trust Anchor Not Found

URI: https://docs.ankatech.co/errors/tsa-trust-anchor-not-found
HTTP Status: 404 Not Found

When you see this

A retire or delete named a trust-anchor id that is not present in the platform's TSA trust-anchor store. Both verbs look the anchor up by id before doing anything else, so the request had no effect. The detail is fixed and never echoes the id, fingerprint, or any certificate metadata.

Common Causes

  • The anchor was already hard-deleted, so its row no longer exists.
  • The id belongs to a different resource, or was copied from a stale console view.
  • The id was mistyped or truncated.

Response Example

{
  "type": "https://docs.ankatech.co/errors/tsa-trust-anchor-not-found",
  "title": "Not Found",
  "status": 404,
  "detail": "The requested trust anchor does not exist.",
  "instance": "/api/v3/admin/platform/tsa/trust-anchors/7f1c2a90-3d44-4b21-9d0e-1c2f6b8a4e55/retire",
  "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 current anchors with GET /api/v3/admin/platform/tsa/trust-anchors and take the id from that response.
  2. Reload the console's trust-anchor view before acting on it — a delete performed elsewhere leaves a stale row on screen.
  3. If the anchor is genuinely gone and it should be trusted, upload the certificate again rather than retrying the retire or delete.

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