Skip to content

Crypto Playground Combination Not Configured

URI: https://docs.ankatech.co/errors/crypto-playground-combination-not-configured
HTTP Status: 422 Unprocessable Content

When you see this

The Cryptographic Playground was asked to run an operation that the named configuration does not allow, so nothing ran. The Admin API resolves every run from the live authorizations of that Exchange or Internal Crypto Use Case: the operation, the Actor, and the Key ID or the ordered source and target pair named in runtimeRequest. When no live authorization matches, the one that matches cannot run now for a reason other than its Actor's status, runtimeRequest names no key of a leg, or the Actor does not hold the operation's Runtime scopes, the request is refused here. A leg whose only obstacle is an Actor that is not active is Crypto Playground Actor Not Active instead.

Returned by POST /api/v3/admin/tenants/{tenantId}/crypto-playground/execute (executeCryptoPlaygroundOperation). The refusal is decided before any token is requested for the Actor and before any audit record is written, so the cryptographic service never sees the request.

Common Causes

  • The configuration changed after the flow was read: an authorization was revoked, expired or used up, or the Exchange or Internal Crypto Use Case was suspended.
  • The request names a key, a key pair or an Actor that the configuration does not hold for that operation.
  • The request names no key: a DECRYPT or VERIFY artifact whose headers name no key or more than one, sent without recipientKid or sourceKid.
  • A re-encrypt or re-sign names its source and target keys the other way round: a pair allows one direction only.

Response Example

{
  "type": "https://docs.ankatech.co/errors/crypto-playground-combination-not-configured",
  "title": "Crypto Playground Combination Not Configured",
  "status": 422,
  "detail": "The configuration does not allow this operation for this Actor and key now, so nothing was run. Refresh the flow and choose one of the legs it lists.",
  "instance": "/api/v3/admin/tenants/8d2f1c4e-3b7a-4e91-a6d5-0c9f2e8b7a14/crypto-playground/execute",
  "extensions": {
    "requestId": "7c9e6679-7425-40de-944b-e07fc1f90ae7"
  }
}

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

How to Resolve

  1. Read the flows again (listCryptoPlaygroundFlows) and run a leg the list shows as runnable.
  2. If the leg you expected is missing or shows a reason it cannot run, correct the Exchange or Internal Crypto Use Case that owns it.
  3. Nothing was run, so running again cannot repeat an operation.

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