How to Use a Signed SSL Certificate with Philter
When Philter is deployed via the AWS Marketplace, Windows Azure Marketplace or other third-party cloud marketplace, SSL will already be enabled via a self-signed certificate. It is recommended you replace this self-signed certificate with a valid certificate issued to your organization by a trusted authority. The instructions for how to do this are described below.
First, create a private key and a certificate signing request (CSR) for Philter on your domain. In this walkthrough we are using the domain philter.yourdomain.com
as an example.
Submit the CSR to your SSL certificate vendor of choice and complete the SSL certificate ordering process. If prompted for a web server during the process, select Apache or Nginx. Once the process is complete and the certificate is issued you will receive a few files. The files you will need are summarized in the table below. The file names may vary and you may also receive other files as well.
File Name | Description | Creator |
---|---|---|
| Certificate signing request | Created by you |
| Certificate private key | Created by you |
| Intermediate certificates provided by the issuing authority | Received from SSL authority |
| The SSL certificate for philter.yourdomain.com | Received from SSL authority |
When prompted for a keystore password we will use changeit
. It's recommended you use a more secure password.
The first thing to do is to convert the certificate and the private key to PKCS12 format in philter.p12
:
Now import the P12 file into a keystore philter.jks
:
Add the intermediate certificate provided by the issuing authority to the keystore:
Update Philter's settings in application.properties
:
Restart Philter:
Execute an API status request to verify Philter is running as expected. With the -v
option we can see the details of the SSL certificate:
Look in the response for details of the certificate. Our domain was philter.mtnfog.dev
: