Configure Curity to use the CryptoHub for TLS

this section covers the tasks to configure curity to integrate with the {{ch}} log in to the {{ch}} from curity you must configure each run time node to communicate with the hsm this requires a pin or password you can provide this interactively on the command line during startup, directly on the command line as an argument, or in the environment variable idsvr hsm pin if you don't provide this pin to each run time node, you cannot log in to the {{ch}} and use keys that reside on the device so, you must start the nodes with this credential the command line argument that you should use is i you can also provide debug hsm in non production environments to get extra hsm related debug log messages in the server log in this case, run the following command to start a node $ idsvr debug hsm i cryptohub identity password enter the password of the identity configured in the fxpkcs11 cfg file in the preceding command warning make sure to follow all the steps in section create a pki container and certificate with key pair on the cryptohub docid\ cxu5rssibkvhkz0zwkwu2 if any steps are skipped, curity will fail to connect to the {{ch}} due to missing tls server certificate configurations (for example, the sha 1 hash signing algorithm hasn't been selected, default approval group isn't defined, or allow object signing hasn't been enabled), even if the key has not yet been selected for use in curity enable and configure the hsm feature in curity to enable using the hsm in curity, perform the following steps log in to the curity admin ui and go to system > general note after running the command to start the curity, the last line of the log will show you which port to connect to scroll down to the hardware security module section and toggle on the hsm after enabling this, you can enter information about how the run time nodes connect to the hsm enter the file path to the {{futurex}} pkcs #11 module in the library field select slot id in the slot field and leave the slot id set to 0 c ommit the changes by selecting commit from the changes menu and selecting \[ ok ] in the deploy changes dialog box configure curity tls settings to use the server key stored in the {{ch}} even without committing the changes, configuring the {{futurex}} hsm for ssl enables you to configure keys similar to those in the hsm to see this, perform the following steps select facilities in the top right corner of the ui go to keys and cryptography > tls , and select the + button next to server ssl keys here, you have three options, including the use from hsm option, which is impossible until an hsm is configured now that the hsm is configured, enter the name of the key created earlier, curity demo 1 , into the name text field note curity uses the java keystore to find the private key stored in the {{ch}} make sure it matches what is found in the response of the keytool command that was ran in the previous section select the use from hsm option and select \[ next ] on the next screen, select rsa from the type drop down list and enter the key size used when the key was made in the hsm, namely 2048 select \[ ok ] c ommit the changes by selecting commit from the changes menu and selecting \[ ok ] in the deploy changes dialog box assign the key assign the key to a run time node by running the following steps go to the system tab and then go to deployments in the sidebar select the name of one of the nodes you have configured to open the update server dialog box the ssl server keystore drop down should be visible if the node uses the https protocol from this list, select the key that you just defined select \[ close ] commit the changes by selecting commit from the changes menu and selecting \[ ok ] in the deploy changes dialog box