Update cs_pkcs11_R<2/3>.cfg file | Utimaco Integration Guides

Example Values:

›_ Console
`[Global]` `# For unix:` `# Logpath = /tmp` `# For windows:` `Logpath = C:/ProgramData/Utimaco/PKCS11_R<2/3>` `# Loglevel (0 = NONE; 1 = ERROR; 2 = WARNING; 3 = INFO; 4 = TRACE)` `Logging = 1` `# Prevents expiring session after inactivity of 15 minutes` `KeepAlive = true` `# Set the Device to connect with` `[CryptoServer]` `# Device specifier` `Device = <HSM_IP>`

›_ Console

[Global]
# For unix:
# Logpath = /tmp
# For windows:
Logpath = C:/ProgramData/Utimaco/PKCS11_R<2/3>
# Loglevel (0 = NONE; 1 = ERROR; 2 = WARNING; 3 = INFO; 4 = TRACE)
Logging = 1

# Prevents expiring session after inactivity of 15 minutes
KeepAlive = true

# Set the Device to connect with
[CryptoServer]
# Device specifier
Device = <HSM_IP>

Use CS_PKCS11_R2 or CS_PKCS11_R3 based on the version of UtimacoPKCS#11 library.
For more information regarding the commands and command parameters please check the CryptoServer documentation. The device may be a CryptoServer (PCIe or LAN) device.
The device line will follow one of these patterns, based on the HSM form-factor:
Device = 288@<HSM IP address> Hardware (LAN) HSM
OR
Device = /dev/cs2.0Hardware (PCIe) HSM

To make your testing easier, it would be good to enable the PKCS#11 log file. That can be enabled by editing the logging loglevel. Specify the LogPath and set Loglevel to 1. For testing you may want to increase it to 4.

The LogPath points to a writable directory, not to a file. If you encounter problems, check the log file cs_pkcs11_R2.log in the under LogPath defined directory. When you are done testing, should change Loglevel to 1 or 2. This will limit the logging to critical and important messages.