Configuring a self-signed SSL certificate

Introduction

Management of Jadaptive products is performed over a secure web page, therefore there is a requirement to have an SSL Certificate configured on your system. When you are ready for production, this should be an officially signed certificate, but for testing purposes, a self-signed certificate is acceptable.

The server will come pre-configured with a self-signed certificate for https://localhost, but note that if you are testing Nodal VPN, the VPN client requires a certificate with a hostname that it can match to its remote connection.

This article shows how you can easily configure a self-signed SSL Certificate.

On a newly deployed system, you may see a pending Setup Task, where you can click Fix to get started.

Or you can navigate to Administration->Setup SSL Certificate.

1. Change Certificate

On the SSL Certificate page, you will be presented with information regarding the currently configured SSL Certificate, note here that the common name is localhost.

Click Change Certificate at the bottom.

Select Generate a self-signed certificate for evaluation, then click Next.

Complete the details form, ensuring the Common Name matches the hostname you will be using for your server. Complete the rest of the form as applies to your organisation. Click Next to continue.

Review the details and click Finish.

Refresh your browser as instructed to load the new certificate.
Note: If this does not work, restart your browser

2. Testing the certificate

Navigate to your server's hostname in your browser. You will see a certificate warning, which is expected as this is not signed.

Inspect your certificate, in Google Chrome for example, click Not Secure in the address bar, then Certificate Details.

You can confirm the Common Name matches the host.