Migrating from Client SDK 3 to Client SDK 5

For detailed instructions on migrating from Client SDK 3 to Client SDK 5, refer to the migration instructions for each individual Client SDK:

• Migrate your PKCS #11 library from Client SDK 3 to Client SDK 5

• Migrate your OpenSSL Dynamic Engine from Client SDK 3 to Client SDK 5

• Migrate your JCE provider from Client SDK 3 to Client SDK 5

• Migrate from Client SDK 3 CMU and KMU to Client SDK 5 CloudHSM CLI

For functionality or use cases that are not supported by CloudHSM CLI, please reach out to support.

Note

Client SDK 5 PKCS #11 library is now supported on Windows platforms. It can handle most the use cases that CNG and KSP providers can and should be considered a replacement. KSP is only available in Client SDK 3 currently.