Possible use of the CaviumKeyStore in client-side TLS

In order to keep the client-side TLS private key in the Cavium keystore, we made a wrapperkeystore at which we keep the certificate, so that we can actually use it to do client-side TLS. Are there actual issues with picking up client-side TLS authentication by the cavium hsm?

Start by reviewing the CloudHSM JCE sample applications and the mentioned CaviumKeyStore and wrapperkeystore approach. Investigate whether the client-side TLS authentication path can use the Cavium HSM, including any issues identified during that review. Done means documenting the compatibility findings and any required scope.

Written by the indexing model from the issue text.