Skip to content

Crypto Playground Delegation Unavailable

URI: https://docs.ankatech.co/errors/crypto-playground-delegation-unavailable
HTTP Status: 502 Bad Gateway

When you see this

The Cryptographic Playground could not obtain a token to run the operation as its Actor, so nothing ran. For every run, the Admin API asks the Auth API, service to service, for a short-lived token for that Actor under the administrator's delegation. This problem is the answer when the Auth API failed, gave an answer that carries no usable token, or could not be reached in time. extensions.upstream names the failing service by its role, authentication-service. extensions.failureSource is DELEGATION and extensions.executionStatus is NOT_EXECUTED: the cryptographic service was never called. extensions.runtimeCorrelationId names the execution, as the operator's audit record and the token request carry it.

Two answers of the Auth API have their own problem instead: a refused delegation is Crypto Playground Delegation Refused (403), and the Auth API's own limit is Crypto Playground Delegation Rate Limited (429).

Returned by POST /api/v3/admin/tenants/{tenantId}/crypto-playground/execute (executeCryptoPlaygroundOperation). The operator's audit record was written before the request for the token, so one record exists with no cryptographic record to match it. The Admin API never retries the request, and nothing of the Auth API's answer is relayed.

Common Causes

  • The Auth API is restarting or unavailable.
  • The Auth API could not read what it needs to decide, such as the roles of the administrator.
  • A network or certificate fault between the Admin API and the Auth API.

Response Example

{
  "type": "https://docs.ankatech.co/errors/crypto-playground-delegation-unavailable",
  "title": "Crypto Playground Delegation Unavailable",
  "status": 502,
  "detail": "The authentication service issued no token to run this operation as the Actor, so the operation was not executed. It is safe to run it again.",
  "instance": "/api/v3/admin/tenants/8d2f1c4e-3b7a-4e91-a6d5-0c9f2e8b7a14/crypto-playground/execute",
  "extensions": {
    "failureSource": "DELEGATION",
    "executionStatus": "NOT_EXECUTED",
    "runtimeCorrelationId": "6f2c1e9a-3d47-4b58-9a10-5e7c2b8d4f36",
    "upstream": "authentication-service",
    "requestId": "7c9e6679-7425-40de-944b-e07fc1f90ae7"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.

How to Resolve

  1. Run the operation again: nothing was executed, and no use was spent.
  2. If every administrator sees it, ask the operator of the environment to check the health of the Auth API.

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