Install VaultCode for testing
In production, VaultCode must run inside a Primus HSM, otherwise it cannot provide the intended security guarantees. However, for testing purposes, VaultCode can be deployed on an external host as a Docker container.
This setup is intended for integration testing only. It is not a production setup. When VaultCode runs outside of the HSM, the HSM cannot provide any guarantees about the runtime environment.
Outside the HSM
Installing VaultCode outside of the HSM is intended for easier integration testing, because it does not require the latest Primus HSM hardware (in particular, it works with X/E-series devices). This mode runs the VaultCode container on an outside host, instead of on the VaultContainers platform. As before, the container connects to an HSM Partition via the JCE interface.
Simulator
As an additional option during testing and integration, VaultCode can run without connecting to an HSM at all. This option is intended to test your custom VaultCode executable without needing to connect to an HSM. You can focus on your executable logic and observe how it performs before connecting VaultCode to your HSM.
When running in this mode you need to configure VaultCode
to run in demo mode.
