PKCS#11 DEVELOPER DOCUMENTATION

Cryptoki integration center

Use the published function, mechanism, object, session and error contracts before linking an application to the provider.

Developer paths

FUN

Functions

Initialization, slot, session, object, key and signature operations.

Open →

MEC

Mechanisms

Classical and controlled PQC/hybrid CKM profiles.

Open →

OBJ

Objects & attributes

Templates, visibility, persistence and policy.

Open →

AUT

Sessions & authentication

Roles, login scope, concurrency, pooling and failover.

Open →

ERR

Return codes

CKR_* causes, retryability and remediation.

Open →

SDK

C samples

Compilable initialization, discovery, sign/verify and cleanup.

Open →

Conformance statement

Release-specific conformance

The website uses PKCS#11 v3.0 terminology as the documentation baseline. Exact Cryptoki conformance, headers, library names, vendor mechanisms and platform builds are defined by the signed release manifest.