mobile menu

Enable HTTPS in MCS

You are here
Enable HTTPS in MCS

Notes

HTTPs support in MyConnection Server (MCS) requires version MCS 10.1a or above

As a best practice this tutorial documents 4 steps to create the MCS certificate file using the Windows platform. The certificate file can be transferred and used with MCS on both Linux and Windows platforms.

We recommend performing these steps on Windows even if MCS is installed on Linux.

Passwords used throughout the process must match and only contain letters and numbers, no special characters.

Overview

The 4 steps to enabling HTTPs/SSL in MCS are as follows:

Notes:

Passwords used throughout the process must match and only contain letters and numbers, no special characters.

Files created during the certificate build steps have been color coded for clarity of use.

Support. If you need help with the SSL certificate application process please email us.

Step 1: Create the combined certificate file

A valid SSL certificate provided by the issuing certificate authority is required for this step. The certificate must consist of 2 files, example yourdomain.com.crt and intermediateCA.crt.

NOTE: Some certificate providers will provide a .PEM file option, for example yourdomain.com.pem. If you have a .PEM file then skip to Step 2.

The two certificate (.crt) files need to be combined together to create a single file as follows:

Step 2: Install and use OpenSSL to package the combined certificate file

This step requires the OpenSSL package for Windows (Note: Scroll down to the Download Win32 OpenSSL section for download links. This is a third party OpenSSL resource that we've found the most reliable but is subject to change) in order to convert the combined certificate file to the OpenSSL PKCS file format.

Step 3: Create the Java compatible Key Store File (.JKS) to be used by MCS

This step requires the Oracle Java keytool utility.

Step 4: Configure MCS so it can find the JKS file