We recommend setting up a dedicated reverse proxy for your Acrolinx Core Platform as a standard security measure. This reverse proxy should be on the same computer as the Core Platform.
A reverse proxy not only ensures that any traffic to your Core Platform is secure, it will also help you avoid other security issues. For example, on Linux a reverse proxy will help you avoid privilege escalations – you can create a dedicated Acrolinx Core Platform user with restricted permissions, and let the reverse proxy listen on ports that require superuser permissions. The Core Platform uses the default ports 80 and 443, which require superuser permissions.
In this article, you'll learn how to set up a reverse proxy for Acrolinx. We use NGINX at Acrolinx, so we've included an NGINX configuration example to show you how we do it. If you're just configuring the proxy for Acrolinx, you can use our example as a template – especially if you're on Standard Stack it should work as is. You can of course use other reverse proxy software if you prefer.
Configuring Your Reverse Proxy
To run your Core Platform behind a reverse proxy, you'll need the following configuration:
- Your proxy server is secured with an SSL certificate. Acrolinx doesn’t support self-signed certificates.
- Your proxy server has Transport Layer Security (TLS) termination enabled.
- Your proxy server adds forwarding information. The following headers are supported:
Forwardedas defined by rfc7239
- The proxy timeout limit is set to at least 360 seconds.
- The proxy server is configured so that the Acrolinx Core Platform has a dedicated domain name.
Example Configuration with NGINX
Below you can see an example configuration for an NGINX reverse proxy. This is the configuration that we use at Acrolinx, and we know it works for Standard Stack installations. If you have a different setup, you can still use this example as a template, but you should adapt it to your specific environment and needs. For the full details on how to set up a reverse proxy with NGINX, take a look at NGINX's own documentation on reverse proxy configuration and TLS termination.
A Tip for SELinux
By default, Red Hat Enterprise Linux runs Security-Enhanced Linux (SELinux) in "Enforcing" mode. This will block NGINX from connecting to Acrolinx's port (8031), unless you allow it.
To allow Acrolinx's port in SELinux, follow these steps:
- Open a command line as root.
getenforce. This checks the mode that SELinux is running in.
If it returns "Disabled" or "Permissive", you don't have to do anything.
If it returns "Enforcing", continue to the next step.
semanage port -l | egrep '(^http_port_t|8031)'. This lists the ports that NGINX is currently allowed to connect to.
If you don't see port 8031 in the output, continue to the next step.
semanage port -a -t http_port_t -p tcp 8031. This adds port 8031 to the security context.
To make sure port 8031 was added successfully, run
semanage port -l | egrep '(^http_port_t|8031)'again.
- Restart NGINX.
If your proxy is serving more than just Acrolinx, make sure you configure
server_name so that Acrolinx has a dedicated domain name with no subdirectories. Some Acrolinx components assume that Acrolinx is running at the top level of the host address. These components won’t work if the Acrolinx URL includes a subdirectory.
Integration-Specific Extra Steps
If you're using any of the following integrations, there are some extra steps: