The Fortanix Self-Defending Key Management Service (KMS) PKCS#11 library for all platforms can be downloaded here
The RPM and DEB installer copies the Fortanix Self-Defending KMS PKCS#11 shared object file (also called library or module) to
The Windows installer installs the PKCS#11 Library, as well as the Fortanix CNG and EKM providers. The default installation location of PKCS#11 library is
You can verify that you can use the Fortanix Self-Defending KMS PKCS#11 library using the
pkcs11-tool utility, which is distributed along with the OpenSC smart card library at https://github.com/OpenSC/OpenSC.
pkcs11-tool --module <module path> --show-info
The expected output is:
Cryptoki version 2.40 Manufacturer Fortanix Library Fortanix Self-Defending KMS PKCS#11 Library (ver 0.3) Using slot 0 with a present token (0x1)
Applications use the Fortanix Self-Defending KMS PKCS#11 library to interact with Fortanix Self-Defending KMS for key management and cryptographic operations. The PKCS#11 specification has notions of slots and tokens, which correspond to physical entities in an HSM. Multiple clients or applications connecting to a token on an HSM have equal access to the entire keyspace. However, Fortanix Self-Defending KMS allows access to several applications simultaneously while guaranteeing strong cryptographic separation of key spaces. This is equivalent to every application having access to its own HSM. Fortanix Self-Defending KMS PKCS#11 library implements this by mapping the application credential to the user PIN, and by having an arbitrarily large number of slots (numbered from 0), with a single token (numbered 1) already initialized. The number of slots defaults to 512 (numbered 0-511) and may be configured through the environment variable
Administration of Fortanix Self-Defending KMS is done using the web UI and using the REST APIs, so the support for doing it through the PKCS#11 library is disabled. PKCS#11 security officer login is disabled, and will always fail with
CKR_PIN_INCORRECT. Similarly, administrative functions such as
C_SetPIN return errors such as
The library can also be used by Java applications using the SunPKCS11 JCE provider. Some examples to build applications using this PKCS#11 library are provided in example code. Please look at our Knowledge Base to learn more about how to configure legacy applications with a PKCS#11 interface to use Fortanix Self-Defending KMS.
C_Login, the API key must be provided as the PIN. Alternatively, the PIN may point to a file to configure additional options. The PIN must have one of the following formats:
- API key (a 164-character string), for example
file://path-to-configuration-file. The path may be absolute (e.g
file:///home/fortanix/pkcs11.cfg) or relative (e.g.
file://pkcs11.cfg). See below for the file format.
env:environment-variable-name. The environment variable may contain the API key directly or specify a file as shown previously.
Configuration file format
The configuration file may contain just the API key on a single line, or it may contain additional options as follows:
api_key = "FEL/ME...j+bt7" api_endpoint = "https://apps.smartkey.io" # default is "https://apps.smartkey.io" fake_rsa_x9_31_keygen_support = false # default is false ca_certs_file = "/path/to/certs.pem" # X.509 PEM CA certificates cert_file = "/path/to/cert.pem" # X.509 PEM client certificate key_file = "/path/to/key.pem" # PKCS#8 PEM client private key app_id = "59be5a1e-8935-4a0a-a272-b0c8512d99f1"
prevent_duplicate_opaque_objects = true
retry_timeout_millis = 3000 [log] system = true # Unix only, logs to syslog file = "/path/to/log/file"
Exactly one of
app_id are required; the other fields are optional and may be omitted. For example, if you don’t want to configure logging, you can omit the entire
By default, the trusted certificates used to verify the connection with the Fortanix Self-Defending KMS server are provided by the system. Additional trusted certificates may be specified by setting the
ca_certs_file configuration option. It must point to a file containing one or more concatenated X.509 certificates in PEM format.
key_file are currently only supported on Linux. If provided, the client certificate and key are used to authenticate to the server. If the app does not have an API key,
app_id must be specified.
fake_rsa_x9_31_keygen_support = true allows the PKCS#11 mechanism
CKM_RSA_X9_31_KEY_PAIR_GEN to be specified when generating RSA keys, even though Fortanix Self-Defending KMS always uses
CKM_RSA_PKCS_KEY_PAIR_GEN. The generated key is fully functional but does not use the X9.31 generation procedure.
Setting the environment variable
FORTANIX_PKCS11_FAKE_RSA_X9_31_KEYGEN_SUPPORT also allows this.
The PKCS#11 library additionally supports the following:
- To prevent creating duplicate opaque objects, set
prevent_duplicate_opaque_objects = truein the config file. This would skip creating new Opaque objects if there is an existing Opaque object with same CKA_LABEL. The default value for
- To configure the error retry limit, set
retry_timeout_millis = xxxxin the config file. Where
xxxxis the value of time in milliseconds. This is the maximum duration for which the PKCS#11 library will do any number of retries in case of API failures from the service. For example,
retry_timeout_millis = 6000sets the retry limit to 6 secs. The default value is
3000, which is 3 secs.
By default, our PKCS#11 library writes logs into Syslog on Linux (typically at
/var/log/syslog on Ubuntu and
/var/log/messages on CentOS) and to the file at
%APPDATA%\Fortanix\KmsClient\pkcs11.log on Windows. Logs can also be redirected to another file in the filesystem specified in the configuration file described above. All the function calls made into the PKCS#11 library are logged in the log file along with their return value. The PKCS#11 log file is useful for debugging and troubleshooting. For additional logging, the environment variable
FORTANIX_PKCS11_LOG_LEVEL can be set to
A connection issue between the PKCS#11 library and Fortanix Self-Defending KMS may cause function calls to fail with the error code
CKR_DEVICE_ERROR. This can be observed in the PKCS#11 log file. If that happens, check for the following:
- Check your network connectivity to ensure that the PKCS#11 library is able to reach Fortanix Self-Defending KMS over TCP port 443.
- Check if the
FORTANIX_API_ENDPOINTenvironment variable is set correctly to point to your Fortanix Self-Defending KMS deployment.
- If you need a web proxy to reach your Fortanix Self-Defending KMS deployment, you can configure it using the env variable
A login failure may be caused by several issues. Follow the following steps to troubleshoot:
- Check if the API Key being used is correct.
- Check if the Fortanix Self-Defending KMS endpoint is set correctly. Fix the
FORTANIX_API_ENDPOINTenvironment variable if API requests are going to an incorrect endpoint.
- Some applications require the PIN for their PKCS#11 library to be limited to a maximum number of characters. The Fortanix Self-Defending KMS API Key is 165 characters long. If this is the case, store the API Key in an environment variable or a file and create a PIN using the appropriate prefix as explained above.