Generate a key pair for the client.
$ keytool -genkey -alias client -keyalg RSA -keystore ./Client.jks -storetype PKCS12
alias = name of the key, for example, client keystore = name of the keystore, for example, Client.jks
When prompted for first and last name the hostname where the certificate is valid should be entered, e.g. localhost. Other values can be anything.
Generate a Certificate Signing Request (CSR) so that we can get client's certificate get signed by a CA.
keytool -certreq -alias client -keystore Client.jks -file Client.csr
Get the certificate signed by our the CA, Test CA in these example. See this page on how to set up a CA.
$ openssl x509 -CA caroot.cer -CAkey cakey.pem -CAserial serial.txt -req -in Client.csr -out Client.cer -days 365
CA, CAkey and CAserial are files generated when setting up the CA.
Import the Test CA's root self signed certificate in client key store as a trusted certificate.
$ keytool -import -alias TestCA -file caroot.cer -keystore Client.jks
Import client's certificate signed by Test CA in client key store with the same alias name that was used to generate the key pair during genkey.
$ keytool -import -alias client -file Client.cer -keystore Client.jks
We also need to import server's public key in the client key store, because Client is the first one who need initiate a conversation with server or the service. And it needs to encrypt the request massage (some part of it) using sever's public key. Server does not need client's public in its keystore if BinarySecurityToken is used, server is going to get the client public key in the SOAP message itself.
$ keytool -import -alias server -file Server.cer -keystore Client.jks