Since version 1.9.8.2.4-1 your DMS can be configured to be accessible only via the https protocol (secure http). In this case, all communication between client computers and the DMS will be secured by encryption.
You can use encryption certificates that are issued by a suitable certificate issuer (eg. https://www.thawte.de, https://www.geotrust.com, https://letsencrypt.org, etc.), or you can use self signed certificates. Note that self signed certificates are generally considered less secure and may require to be trusted by the browsers used to access the DMS server. Please find a short guide how to create a self signed certificate here.
Note: If you wish to update an older version of the DMS (pre 1.9.8.2.4-1) to a version supporting https, please contact Patrix of Practice Insight before you run the update to make sure that all relevant modifications to the configuration files of your client specific git repository have been made.
In order to configure your DMS to use secured communication, the following steps must be taken:
Create a directory that will hold the certificate- and key-files ('<certificateName>.cer' and '<certificateName>.key'). For example you can run
mkdir /storage/nginx/
- Obtain a certificate- and key-file from one a certificate issuer or create a self signed certificate- and key-file and move them to the directory that was just created.
- Update your deploy scripts (Auto-deploy script section Script updates).
- Uncomment and edit the
dms.conffile in the client specific git repository in the section 'HTTPS parameters'. In addition, make sure the NUXEO_URL in this file does not specify a port number. - In the PAT_DMS_SETTINGS table, set the key https.enabled to true (if this key is not present, add it).
- Run the deploy command for all containers.
Trusting self signed certificates in InterNet Explorer: https://www.ibm.com/support/knowledgecenter/en/SSYQBZ_9.6.1/com.ibm.rational.dwa.install.doc/topics/t_configureIEforSSL.html