Remove the default self-signed certificate

1. Take a snapshot of the Commander app server before making changes.
2. Open a command prompt on the Commander server and browse to:

   <INSTALL DIRECTORY>\Embotics\vCommander\jre\bin
   

3. Delete the existing certificate using:

   keytool -delete -alias tomcat -keystore "C:\Program Files\Embotics\vCommander\tomcat\conf\keystore" -storepass changeit

   • Enclose paths with spaces in quotes.
   • If the Commander service was stopped before deletion, do not restart until a new certificate is installed.

Generate a new self-signed certificate

1. In the same directory, run:

   keytool -genkey -alias tomcat -keyalg RSA -keysize 2048 -sigalg SHA256withRSA -validity 3650 -keystore "C:\Program Files\Embotics\vCommander\tomcat\conf\keystore" -storepass changeit

2. Enter the required details when prompted:
   • First and Last Name: Fully qualified domain name (FQDN) of the server.
   • Organizational Unit: Department name.
   • Organization: Organization name.
   • City, State, Country Code as appropriate. (List of country codes)
3. For Key Password, press ENTER to leave blank as recommended.
   
4. Restart the vCommander service if stopped earlier.

Import CA-signed certificates

1. Save the CA-provided .crt file to the same directory used above.
2. Run:

   keytool -import -trustcacerts -alias tomcat -file yourfile.crt -keystore ..\..\tomcat\conf\keystore -storepass changeit

3. If intermediate certificates are required, install them first as per CA instructions.
4. Look for the message Certificate reply was installed in keystore. Restart the vCommander service.

Important

If you encounter java.io.EOFException, ensure the certificate file has no trailing spaces or extra characters, then retry.

Outcome

After completing these steps, Snow Commander will use a CA-signed certificate, eliminating browser trust warnings for users.