You may wish to install can configure Tomcat to support secure connections over SSL , that is, via HTTPS.This via HTTPS. PhixFlow recommends you always use HTTPS communication between Tomcat and the PhixFlow webapp. However, if you are running Tomcat and PhixFlow behind a secure firewall, you may prefer to use HTTP communication.
Configuring HTTPS is described in the standard Tomcat documentation - for tomcat 8 at . For Tomcat 8, see https://tomcat.apache.org/tomcat-8.0-doc/ssl-howto.html - but some notes are given here to get you started. This page provides an overview of the process.
Type of
...
Certificate
If access to PhixFlow is only intended for people in your organisation, you may wish to create a self-signed certificate. This still provides a secure connection, but this will generate security warnings when users first connect, and they will not see a padlock in the address bar of their browser. If this is not acceptable to your users or by your company policy, or if you are going to provide access to people outside your organisation, you should obtain your certificate from a certificate authority (CA).
A list of certificate authorities is given in https://en.wikipedia.org/wiki/Certificate_authority.
...
Steps
The installation of a certificate will contain the steps:
...
These instructions will help you get an HTTPS connection to PhixFlow, using a self-signed certificate, on linux Linux and windowsWindows.
| Warning |
|---|
These quick start instructions will allow you to connect to PhixFlow over an HTTPS connection, but there are other security implications when setting up a production system using certificates - in particular, whether you use a certificate from a certificate authority. Therefore, you may need to check this set up against your company security policies. Consult the standard tomcat documentation for full details. |
...