Mobile-ID Quantum Safe
Open Demo Lab

WINDOWS PROVIDER DOCUMENTATION

Windows CNG/KSP & CSP/CAPI integration center

Start with the application API surface. Do not assume a CNG/KSP build satisfies a legacy CSP/CAPI consumer.

01

Choose the correct integration path

KSP

CNG/KSP — NCrypt

Modern Windows storage-provider path for persisted keys, signing and certificate binding.

Open →
CSP

CSP/CAPI compatibility

Legacy CryptoAPI applications require a separate compatibility decision and test record.

Open →
ENR

Certificate enrollment

certreq, CertEnroll, certificate-store binding, renewal and re-binding.

Open →
APP

Application compatibility

Tested combinations of OS, provider build, backend and consumer application.

Open →
DIA

Troubleshooting

Logs, errors, retry rules, rollback and support-bundle collection.

Open →
SDK

Samples

C++, C#, PowerShell and certreq examples for controlled evaluation.

Open →

02

Release acceptance checklist

  • Exact Windows build and architecture recorded.
  • Provider package and signer checksum verified.
  • Key backend and authentication policy fixed.
  • NCrypt/CAPI contract selected explicitly.
  • Positive, negative and rollback tests completed.
  • Consumer application version included in the interoperability record.