Functional Testing
-
Trigger the discovery scan from Qinsight Atlas.
-
Verify that Qinsight authenticates with RCAPI and retrieves a Bearer token.
-
Fetch key attributes from the HSM simulator via RCAPI and confirm that the expected cryptographic objects are visible in Qinsight Atlas.
Performance Benchmarks
Operations performed through the RCAPI server demonstrate low latency for key fetching and creation tasks.
Logs and Validation Steps
PKCS#11 Logs
Enabling PKCS#11 logging to facilitate easier testing and troubleshooting is recommended. This can be done by configuring the Logging Loglevel and LogPath parameters in the configuration file.
-
LogPath should point to a writable directory (not a specific file) where log files can be stored.
-
Set it to 1 for basic logging.
-
For detailed testing and debugging, increase the level to 4.
-
The generated log file will be named cs_pkcs11_R3.log and located in the directory specified by LogPath. Reviewing this log file can help identify and resolve issues that arise during testing.
Once testing is complete, it is advisable to reduce the Logging Loglevel to 1 or 2 to limit logging to only critical or important messages, thereby optimizing performance and reducing unnecessary log data.
Qinsight Atlas Logs
Review Docker container logs for the RCAPI Server. Additionally, Qinsight client logs will capture detailed HTTP response codes.