Skip to content
Settings

TRUSTED_KEY_NOT_FOUND — referenced trusted key does not exist

cyoda-go version 0.7.1

TRUSTED_KEY_NOT_FOUND — an admin operation referenced a trusted-key KID that is not present in the registry.

HTTP: 404 Not Found. Retryable: no.

Returned by trusted-key admin endpoints when the supplied KID does not match any registered key:

  • DELETE /oauth/keys/trusted/{keyId} — the deletion target does not exist.
  • POST /oauth/keys/trusted/{keyId}/invalidate — the lifecycle target does not exist.
  • POST /oauth/keys/trusted/{keyId}/reactivate — the lifecycle target does not exist.

The detail field carries a generic key not found message; internal store phrasing (e.g. backend-specific KID echoes) is never leaked into the response body. Operators can correlate the request via the slog event emitted server-side at INFO level with kid and the underlying error.

Not retryable. Verify the KID via GET /oauth/keys/trusted before retrying the operation.

  • errors
  • errors.UNAUTHORIZED
  • errors.FORBIDDEN
  • cyoda help errors — Every error response from the Cyoda REST API carries a structured errorCode in the properties object. Multiple codes may share the same HTTP status. Programmatic handling keys on errorCode, not HTTP status.
  • cyoda help errors UNAUTHORIZED — Returned when the Authorization header is missing, the bearer token is expired, the token signature is invalid, or the token was issued by an untrusted issuer. Also returned when a request reaches a protected route with no identity context established by the auth middleware.
  • cyoda help errors FORBIDDEN — The request was authenticated successfully but the caller’s JWT claims do not include the role required by the endpoint (for example, admin is required for administrative operations). Tenant mismatch — where the caller’s tenant does not match the resource — also produces this error.