Configure KMES Series 3

this section starts with general configurations you must make on the {{k}} to enable versasec vsec\ cms to integrate with the {{k}} for storing the master key(s) used when performing administration key operations with the vsec\ cms, such as registering a credential or pin unblock operations then, it covers the necessary steps to configure tls communication between the {{k}} and the vsec\ cms instance configure general {{k}} settings for integration with vsec\ cms perform the following tasks to configure the {{k3}} for communication with signtool create a verasec role and identity with the correct assigned permissions enable host api commands the following sections show you how to complete these tasks create a role and identity perform the following steps to create a new role and identity for vsec on the {{k3}} with the required permissions a later section shows you how to configure them in the {{futurex}} pkcs #11 configuration file log in to the {{k3}} application interface with the default admin identities go to identity management > roles and select \[ add ] at the bottom of the page on the info tab of the role editor window, specify a name for the role and set the number of logins required to 1 on the permissions tab, enable the following permissions permission subpermission cryptographic operations sign, verify, encrypt, decrypt keys add, export on the advanced tab, configure allowed ports to host api only select \[ ok ] to finish creating the role go to identity management > identities , right click anywhere in the window, and select add > client application on the info tab of the identity editor window, select application for the storage location and specify a name for the identity on the assigned roles tab, select the role you just created on the authentication tab, configure the password select \[ ok ] to finish creating the identity enable the host api commands because the {{futurex}} pkcs #11 library connects to the host api port on the {{k}} , you must define which host api commands to enable for the fxpkcs11 library to enable the ehost api commands required for vsec\ cms operation, complete the following steps log in to the {{k3}} application interface with the default admin identities go to administration > configuration > host api options and enable the following commands command description or subcommand (if applicable) atkg manipulate hsm trusted asymmetric key group add add hsm trusted asymmetric key group modify modify hsm trusted asymmetric key group delete delete hsm trusted asymmetric key group get retrieve hsm trusted asymmetric key group echo communication test/retrieve version rafa filter issuance policy rkcp get command permissions get retrieve enabled commands modify update enabled commands rkcs create symmetric hsm trusted key group rkdp delete asymmetric hsm trusted key rked encrypt or decrypt data rkln lookup objects rklo login user rkpk pop generated key rkrc get hsm trusted key rkru rsa unwrap the symmetric key time set time select \[ save ] to finish configure tls communication perform the following tasks to configure tls communication between the {{k3}} and the vsec\ cms instance create a certificate authority generate a csr for the system/host api connection pair sign the system/host api csr export the root ca certificate export the signed system/host api tls certificate load the exported certificates into the system/host api connection pair issue a client certificate for vsec\ cms export the vsec\ cms certificate as a pkcs #12 file the following sections describe how to perform these tasks create a certificate authority perform the following steps to create a certificate authority (ca) log in to the {{k3}} application interface with the default admin identities go to pki > certificate authorities and select \[ add ca ] at the bottom of the page in the certificate authority window, enter a name for the certificate container, leave all other fields as the default values, and select \[ ok ] the certificate container you created now displays in the certificate authorities menu right click the certificate container and select add certificate > new certificate on the subject dn tab, set a common name for the certificate, such as system tls ca root on the basic info tab, leave all of the default values set on the v3 extensions tab, select the certificate authority profile and select \[ ok ] the root ca certificate now displays under the previously created certificate container generate a csr perform the following steps to generate a csr for the system/host api connection pair go to administration > configuration > network options in the network options window, go to the tls/ssl settings tab under the system/host api connection pair, uncheck the use futurex certificates checkbox and select \[ edit ] next to pki keys in the user certificates section in the application public keys window, select \[ generate ] when warned that ssl will not be functional until new certificates are imported , select \[ yes ] to continue in the pki parameters window, leave the fields set to the default values and select \[ ok ] the application public keys window now shows that a pki key pair is loaded select \[ request ] on the subject dn tab, set a common name for the certificate, such as kmes on the v3 extensions tab, select the tls server certificate profile on the pkcs #10 info tab, select a save location for the csr and select \[ ok ] when notified that the certificate signing request was successfully written to the file location that was selected , select \[ ok ] select \[ ok ] again to save the application public keys settings the main network options window now shows loaded next to pki keys for the system/host api connection pair sign the csr perform the following steps to sign the system/host api csr go to pki > certificate authorities right click the system tls root ca certificate you created and select add certificate > from request select the csr you generated for the system/host api connection pair in the file browser after it loads, don't modify any settings for the certificate select \[ ok ] the signed system/host api certificate now shows under the root ca certificate on the certificate authorities page export the root ca certificate perform the following steps to export the root ca certificate go to pki > certificate authorities right click the system tls ca root certificate and select export > certificate(s) in the export certificate window, change the encoding to pem and select \[ browse ] in the file browser, go to the location where you want to save the root ca certificate specify a name for the file and select \[ open ] select \[ ok ] a message box states that the pem file was successfully written to the location that you specified export the host api certificate perform the following steps to export the signed system/host api certificate go to pki > certificate authorities right click the system/host api tls certificate and select export > certificate(s) in the export certificate window, change the encoding to pem and select \[ browse ] in the file browser, go to the location where you want to save the system/host api certificate specify a name for the file and select \[ open ] select \[ ok ] a message box states that the pem file was successfully written to the location that you specified load the exported certificates perform the following steps to load the exported certificates into the system/host api connection pair go to administration > configuration > network options in the network options window, go to the tls/ssl settings tab under the system/host api connection pair, select \[ edit ] next to certificates in the user certificates section right click the system/host api ssl ca x 509 certificate container and select \[ import ] select \[ add ] at the bottom of the import certificates window in the file browser, select both the root ca certificate and the signed system/host api certificate, and select \[ open ] select \[ ok ] to save the changes in the network options window, the system/host api connection pair shows signed loaded next to certificates in the user certificates section select \[ ok ] to save and exit the network options window issue a client certificate perform the following steps to issue a client certificate for vsec\ cms a later section shows how to configure it in the futurex pkcs #11 configuration file go to pki > certificate authorities right click the system tls ca root certificate and select add certificate > new certificate on the subject dn tab, set a common name for the certificate, such as vsec leave all fields on the basic info tab set to the default values on the v3 extensions tab, select the tls client certificate profile and select \[ ok ] the vsec certificate now displays under the system tls ca root certificate export the vsec\ cms certificate to perform the following steps, you must go to administration > configuration > options and enable the allow export of certificates using passwords option perform the following steps to export the vsec\ cms certificate as pkcs #12 file go to pki > certificate authorities right click the vsec certificate and select export > pkcs12 select the export selected option, specify a unique name for the export file, and select \[ next ] choose and enter a file password and select \[ next ] select \[ finish ] to initiate the export move both the vsec certificate and the root ca certificate that was exported in the export the root ca certificate section to the computer that runs the vsec\ cms instance a later section shows how to configure and use them for tls communication with the {{k3}}