Validate and test

this section explains how to test and validate curity is integrated with {{k3}} for storing the private keys before starting this section, install and configure curity per your specific requirements validate success if things worked and you logged at the debug level, you should see log messages like the following sample in the run time nodes logs name = idsvr hsm 	library = /usr/local/bin/fxpkcs11/libfxpkcs11 so 	attributes = compatibility 	slotlistindex = 0 	showinfo = true sunpkcs11 initializing pkcs#11 library /usr/local/bin/fxpkcs11/libfxpkcs11 so sunpkcs11 login succeeded pkcs11keystore enginegetentry found private key entry aliases in hsm \[demo 1] hsm is loaded notice the following elements the configured library was loaded which slot list index was used the login with the pin worked the hsm has one key with the alias curity demo 1 this means that ssl now uses a key from the hsm test the connection to test this, open a connection to the node with a browser or openssl by running the following command echo | \\ openssl s client connect localhost 8443 showcerts | \\ openssl x509 inform pem noout text this should output info about the self signed cert imported onto the {{futurex}} kmes, including a line like this depth=0 cn = demo 1