Skip to content

Unsupported Keystore Format

URI: https://docs.ankatech.co/errors/unsupported-keystore-format
HTTP Status: 400 Bad Request

When you see this

The keystore you uploaded is in a format the platform does not support for this operation.

Common Causes

  • Uploading a keystore type other than the supported PKCS#12 / JKS formats.
  • A corrupted or truncated keystore file that cannot be recognized.
  • Mislabeling the keystore format in the request.

Response Example

{
  "type": "https://docs.ankatech.co/errors/unsupported-keystore-format",
  "title": "Unsupported Keystore Format",
  "status": 400,
  "detail": "The supplied keystore format is not supported. Expected PKCS#12 or JKS.",
  "instance": "/api/v3/admin/tenants/2f1c9d84-6b2e-4d3a-9f57-0a1b2c3d4e5f/keys/import-keystore",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details (which obsoleted RFC 7807; the media type is unchanged).

Note the correlation member. Admin API nests it as extensions.requestId; Core API and the PQC Handshake API carry a top-level correlationId instead. This type is raised by core-api and relayed by admin-api, and under the relay contract the instance and the correlation id are always the responding service's own — so the shape above is admin-api's, matching the route in instance. See Where extension members live.

How to Resolve

  1. Convert the keystore to a supported format (PKCS#12 or JKS) before uploading.
  2. Confirm the file is complete and not corrupted.
  3. Verify the declared format matches the actual file and re-submit.

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