FileCatalyst Workflow and Webmail all versions.
This article will give a quick walkthrough of the installation procedure or the upgrade of an SSL Certificate with the generation of a Certificate Signing Request (CSR).
For an additional fee, our FileCatalyst Support team can assist you with this process. Please contact your account representative for more details. This fee is waived if the SSL Certificate is purchased from FileCatalyst. We use Thawte as our Trusted Certificate Vendor.
These instructions assume you acquired your full certificate chain from Thawte and that steps from another provider may differ.
Note: To renew or upgrade an existing certificate please follow the same steps as for a new certificate, however, use a different name for the keystore file, for example, -keystore .keystoreNew
Note: For the purposes of this article we will reference a Windows Environment and related file paths.
Install Java JDK:
Use the following guide to Install the Java Development Kit (JDK) on your Operating System: http://docs.oracle.com/javase/8/docs/technotes/guides/install/install_overview.html
- Generating the keystore file:
By default Tomcat will expect password to be "changeit". If you choose a different password you will have to make an additional change in the server.xml file.
Open a Command Prompt.
- Navigate to the bin directory located inside the JDK Install location. A sample path looks like C:\<Path to JDK installation>\bin\
- Create a new folder on your system to store the Tomcat SSL. We used the following command:
- Navigate to the Tomcat-SSL directory, by using the command:
- Steps to Java Keystore File:
- Use the keytool command to create the CSR. Use the following command to execute the process:
keytool -keysize 2048 -genkey -keyalg RSA -alias tomcat -keystore .keystore
- The following prompts will be displayed. Fill them out with your Company’s information:
- Enter keystore password: changeit
- What is your first and last name?
[Unknown]: Must contain fully qualified domain name e.g.: www.mydomain.com
- What is the name of your organizational unit?
[Unknown]: FileCatalyst Testing (example)
- What is the name of your organization?
[Unknown]: FileCatalyst (example)
- What is the name of your City or Locality?
[Unknown]: Ottawa (example)
- What is the name of your State or Province?
[Unknown]: Ontario (Must contain no abbreviations)
- What is the two-letter country code for this unit?
[Unknown]: CA (example)
- Is CN= www.mydomain.com , OU= FileCatalyst testing , O= FileCatalyst , L= Ottawa, ST= Ontario , C= CA correct?
- Enter key password for <tomcat>
Press Enter if same as keystore password. Please specify the same password (changeit) for the .keystore and the keyEntry. If there was an error in the process you will receive the following error message when you restart the Tomcat Engine:
java.security.UnrecoverableKeyException: Cannot recover key
Observe that a .keystore file was created.
Run the following command to make sure you can read the .keystore file:
keytool -list -keystore .keystore
- The .keystore will be stored in the C:\<Path to JDK installation>\bin\ directory or C:\Tomcat-SSL\ depending on how your PATH environmental variable is set. If the file is located in C:\<Path to JDK installation>\bin\ copy it to C:\Tomcat-SSL\.
- Create a copy of the .keystore file and store it on a removable disk for safekeeping in case of a server crash.
- Generate a CSR of the newly created .keystore and keyEntry:
- Open the Command Prompt.
- Navigate to the Tomcat-SSL directory, by using the command:
- Run the following keytool command in a Command Prompt:
keytool -certreq -alias tomcat -keyalg RSA -file <newcertreqname>.csr -keystore .keystore
- You will be prompted to enter the keystore password. The following output will be observed:
Enter keystore password: changeit
The CSR will be saved to your C:\Tomcat-SSL\ directory
-----BEGIN NEW CERTIFICATE REQUEST-----
-----END NEW CERTIFICATE REQUEST-----
- Send the CSR file to your Certificate Authority (CA). If you want to use a self-signed SSL certificate, you can skip this step and proceed to step 7. A self-signed certificate will always display a warning to the end user that the certificate is not valid since it was not issued by a Certificate Authority. This type of SSL certificate will also affect some Java web applications including UnlimitedFTP Servlet, FileCatalyst Webmail, and FileCatalyst Workflow.
- Certificate Download and Format:
- When you receive the certificate from the Certificate Authority, download it in PKCS#7 format.
- Open the signed Certificate in Notepad or a text editor.
- If you obtained a certificate and it was not sent to you in PKCS#7 format, you must do these additional steps:
- Copy and paste the signed certificate from the email into Notepad or a text editor.
- Save the certificate as <yourcertname>.cer file.
- Double-click on the <yourcertname>.cer file and click on Install Certificate.
- Place the Trusted Certificate in your Personal Store.
- For Thawte certificate, download the Primary and Secondary Intermediate CAs for SSL 123. Make sure you download them as a .cer format.
- Install them by repeating steps 5c-iii.
- Open the Run Command on your computer and type in Certmgr.msc to open the Certificate Manager.
- Under Certificate for Current User, select Personal and expand the Certificates Folder.
- You should see your certificate that you imported as well as Thawte’s Primary and Secondary Intermediate Certificates.
- Right-Click on your certificate. Click on All Tasks, then hit Export.
- Select Cryptographic Message Syntax Standard - PKCS #7 Certificate (.p7b) and make sure to check Include all certificates in the certification path if possible.
- Save the file as <certname>.txt, under the C:\Tomcat-SSL\folder.
- Import the Certificate into the .keystore:
- Run the following command to import the signed certificate into the .keystore:
keytool -import -alias tomcat -trustcacerts -file <certname>.txt -keystore .keystore
- Deploy the Trusted Certificate and .keystore into Tomcat:
- Tomcat keeps its configuration information in the <PathtoTomcatHome>\conf\server.xml file, make sure that port 8443 is not already in use and that it is enabled on your firewall. Using a text editor open server.xml file and make the changes to the Connector:
<Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol" SSLEnabled="true"
maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keystoreFile="<Path-to-keystore>/.keystore" keystorePass="changeit"/>
Specify the path to your keystore file in keystoreFile="c:\tomcat-ssl\.keystore". If your keystore password is not "changeit" then make the change to keystorePass="changeit" in the factory element. If a specific port does not need to be specified in the URL, such as https://mycompany.com:<port>, then port 443 should be specified in the connector. This change will provide seamless integration.