Note
CNG Key Stores are only compatible with Windows Server installations
The Cryptography API: Next Generation (CNG) works with key storage through a number of Key Storage Providers (KSPs)that do the actual work of storing keys. Devices such as Hardware Security Modules (HSMs) and cryptographic USB tokens mayprovide a CNG KSP that can be used to communicate with the device.
Every CNG KSP is identified by a name. If using an HSM or crypto token, refer to the device's documentationto find the name and type of the KSP. Additionally, see the section below for common KSP names.
To configure a CNG key store on Amplia, use the following settings:
- Type:
CNG - ProviderName: name that identifies the KSP to be used
- UseMachineStore: some KSPs have the concept of storing keys on the user store or on the machine store (most notably the OS's native KSP).By default, the user store is used. Set this setting to
trueto use the machine store. - Pin: the PIN of the store, if required
Example (.ini or .conf configuration file):
[KeyStores:MyCngKeyStore]Type=CngProviderName=...Example (environment variables):
KeyStores__MyCngKeyStore__Type=CngKeyStores__MyCngKeyStore__ProviderName=...Example (.json configuration file):
"KeyStores": { ..., "MyCngKeyStore": { "Type": "Cng", "ProviderName": "..." }, ...}Common CNG key stores
Safenet eToken cryptographic USB token:
"CngToken": { "Type": "Cng", "ProviderName": "SafeNet Smart Card Key Storage Provider"}