Testing the WSOP Server

From the root user’s home directory, use the curl utility to verify the WSOP application server is working correctly and is properly accessing the Hardserver for key information:

# curl --cacert server-cert.pem --cert ./client-cert.pem --key client-key.pem --header 'Accept: application/json' “https://<wsop-host>:18001/km/v1/keys”

{"keys":[{"created":"2019-10-02T03:09:54Z","kid":"urn:uuid:a22071d9-8ace-3a67-ac59-61129fb8f46b","sworldAppname":"simple","sworldIdent":"key1"}]}

# curl --cacert server-cert.pem --cert ./client-cert.pem --key client-key.pem --header 'Accept: application/json' “https://<wsop-host>:18001/km/v1/keys”

{"keys":[{"created":"2019-10-02T03:09:54Z","kid":"urn:uuid:a22071d9-8ace-3a67-ac59-61129fb8f46b","sworldAppname":"simple","sworldIdent":"key1"}]}

The key returned was the simple 256-bit AES key added in the previous step. If the command was successful, we know the WSOP service is correctly configured and properly responding to requests.

the kid field – we’ll use this in the next step when we add the HSM to DataCore vFilO.