Skip to content

Cryptographic Failure

URI: https://docs.ankatech.co/errors/crypto
HTTP Status: 500 Internal Server Error

When you see this

A cryptographic operation failed for a reason the platform could not attribute to your request. This is the server-fault type: it means the failure was not classified, not that it was caused by something you sent.

This is not a retryable condition

A 500 from this type is a server fault, not a transient one. Retrying the identical request will produce the identical result. If a condition really is transient, it is reported as a 503 with a Retry-After header, not as this type.

What does not arrive here

Client-caused conditions are not reported under this type. A condition that has an owning error type reaches you as that type, with its own status:

Common Causes

What remains under this type is genuinely server-side:

  • A cryptographic provider or JCA/Bouncy Castle primitive failed unexpectedly during the operation.
  • A keystore entry could not be read or deserialized because of a storage-layer fault.
  • An internal invariant was violated while assembling or disassembling a JWE/JWS structure.

How to Resolve

  1. Do not retry. The condition is not transient, and retrying a mutating operation is never safe.
  2. Record the correlationId from the response body (and the X-Correlation-Id response header) — it is the only key that ties your request to the server-side log entry, which carries the diagnosable cause. The response body deliberately does not.
  3. Report the correlationId, the endpoint and the approximate timestamp to your administrator or to AnkaSecure support.

Dispatch on the type URI, never on the wording of detail. See Error Reference for the full type registry.