Skip to content

SDK — Downloads

Package: AnkaSecure SDK (data plane)
Coordinate: co.ankatech:ankasecure-sdk:3.4.0 (Maven Central)
Artifact: ankasecure-sdk-3.4.0.jar
Version: 3.4.0
Java required: 17+

The SDK is a single JAR with no runtime dependency on the platform's internal libraries. It performs the data-plane operations against keys that already exist in your tenant; managing those keys and the grants over them is the Key Management SDK's domain.

Two ways to obtain it, and most integrations want the first:

  1. A Maven or Gradle dependency resolved from Maven Central — see Maven Central. Nothing on this page needs to be downloaded by hand.
  2. The JAR itself, for a build that cannot reach Maven Central: an air-gapped environment, a locked-down CI image, or a classpath assembled by hand. Central and this page serve the same bytes for a given version.

Maven Central

Maven

<dependency>
    <groupId>co.ankatech</groupId>
    <artifactId>ankasecure-sdk</artifactId>
    <version>3.4.0</version>
</dependency>

Gradle

implementation 'co.ankatech:ankasecure-sdk:3.4.0'

Maven Central is the only repository the build needs: every transitive dependency of the SDK resolves from it. Each published version carries the JAR, its sources and Javadoc JARs and its POM, each with an .asc signature made with the AnkaTech release key, whose public key is published on keys.openpgp.org and keyserver.ubuntu.com. A version on Central is immutable: it is never replaced or withdrawn.

Library

Artifact Download Description
SDK ankasecure-sdk-3.4.0.jar The library, ready for the classpath
Javadoc ankasecure-sdk-3.4.0-javadoc.jar API reference, attachable in your IDE

Postman collection

Artifact Download Description
Postman collection ankasecure-v2.postman_collection.json Every data-plane endpoint as a request, grouped by tag; generated from the same OpenAPI document the SDK is built from

Import it into Postman and set the collection variable baseUrl to your platform's API origin. The requests carry no credential: obtain an access token from the Auth API and add it as a Bearer authorization at the collection level, so every request inherits it.

File integrity verification

Artifact Checksum
ankasecure-sdk-3.4.0.jar .sha256
ankasecure-sdk-3.4.0-javadoc.jar .sha256
ankasecure-v2.postman_collection.json .sha256 
sha256sum -c ankasecure-sdk-3.4.0.jar.sha256

The complete lists are also published as sha256sums and md5sums.

Past releases

Every published version keeps its own permanent path, /downloads/sdk/<X.Y.Z>/, and its files are never replaced or removed. The links above name the release this documentation version was built from; the version selector at the top of the page opens the downloads page of another version.

  • Every published version of the SDK — newest first, each version with its files and their SHA-256 checksums.
  • /downloads/sdk/latest/<file> redirects to <file> in the greatest published version, and /downloads/sdk/latest/ to that version's entry in the listing. File names carry their version, so a script that must always fetch the newest release reads the component's latest from the releases index below and then fetches the versioned path; a reproducible build pins a version instead.
  • /downloads/releases.v1.json is the machine-readable index of every version of every component this site publishes (schemaVersion 1; per file its name, size and SHA-256).

Compatibility with newer servers

From 3.2.0 the SDK's generated models ignore a response member they do not declare, so a server of a later release that adds a member to a response does not break a client built on an earlier SDK. A required member that is missing, or a member of the wrong type, is still refused. The ignored member is not kept: a model read from a response and sent back in a request carries only the members the SDK declares.

One exception remains. The 400 body of the token endpoint can take one of several shapes with no discriminator member, and is told apart by each shape's exact member set, so a member the SDK does not declare inside it still matches no shape and the response is refused.

An SDK before 3.2.0 refuses any response carrying a member it does not declare. Upgrade a 3.1.x SDK, and the Crypto CLI that embeds it, together with the server when the server moves to 3.2.0 or later.

Next steps