Reverse Proxy Configuration

Use the following a2enmod script to enable the headers, rewrite, proxy_http, ssl, and http2 modules:

$ a2enmod headers
$ a2enmod rewrite
$ a2enmod proxy_http
$ a2enmod ssl
$ a2enmod http2

Add the following directives to the VirtualHost section of a relevant .conf file:

Protocols h2 http/1.1

RequestHeader set X-Forwarded-Proto "https"

DefaultType none

RewriteEngine on
AllowEncodedSlashes on

RewriteCond %{QUERY_STRING} transport=polling
RewriteRule /(.*)$ http://127.0.0.1:1111/$1 [P]

ProxyRequests off

ProxyPass / http://127.0.0.1:1111/
ProxyPassReverse / http://127.0.0.1:1111/

SSLEngine On
SSLCertificateFile <path_to_certificate>
SSLCertificateKeyFile <path_to_key>

Set the following variables to match your Hub configuration:

• Replace 1111 with the actual port number that your Hub server listens to.

• Set the value for the <path_to_certificate> to the location of the SSL/TLS certificate for your server.

• Set the value for the <path_to_key> to the location of the PEM-encoded private key file for the server certificate.

Add the additional HSTS header to the HTTPS VirtualHost directive. Max-age is measured in seconds.

# Guarantee HTTPS for 1 Year including subdomains
Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"

Note that this header is only valid on a HTTPS VirtualHost.

Add a server-side redirect to upgrade non-HTTPS connections the first time the site is accessed. Add this to the non-HTTP VirtualHost.

[...]
ServerName myHubService.com
Redirect permanent / https://myHubService.com/

Replace myHubService.com with the actual domain name of your Hub server.

Download and install the Application Request Routing (ARR) extension from the Microsoft website.

In IIS Manager, connect to the IIS server - in this case, localhost.

Highlight the server in the Connections pane.

Double-click URL Rewrite.

Click View server variables in the right pane.

Add the following server variables to the list:

HTTP_X_FORWARDED_HOST
HTTP_X_FORWARDED_SCHEMA
HTTP_X_FORWARDED_PROTO

Highlight the server in the Connections pane.

Double-click Application Request Routing Cache.

Click Server Proxy Settings under the Proxy heading in the Actions pane.

Select the Enable proxy checkbox.

Deselect the Reverse rewrite host in response headers checkbox, then click Apply.

In the Connections pane, under Sites, select Default Web Site.

Double-click the URL Rewrite feature, then click Add Rule(s) in the Actions pane.

Add a reverse proxy rule with the server name: localhost:1111 (replace with the real location and port of your Hub service).

Open the rule, check the rewrite URL, and add the following server variables:

• Set the HTTP_X_FORWARDED_HOST variable to {HTTP_HOST}.

• Set the HTTP_X_FORWARDED_SCHEMA variable to https.

• Set the HTTP_X_FORWARDED_PROTO to https.

Make sure that anonymous authentication is enabled:

• In the Sites section of the Connections pane, select Default Web Site.

• Double-click Authentication, select Anonymous, then click Enable in the right pane.

Add a new SSL binding to the Default Web Site.

• The address that the SSL binding listens to (Host URL) should match the Hub base URL.

• The certificate that you choose should correspond to the server DNS address.

Configure the HTTP Strict Transport Security (HSTS) settings for the Default Web Site

• Set the enabled attribute for the <hsts> to true.

• Specify a value for the max-age attribute. For example, 31536000 (one year, in seconds).

• Set the values for the includeSubDomains and redirectHttpToHttps to true as well.

For specific instructions, please refer to the IIS configuration reference.

Open the configuration file for your NGINX server. By default, the configuration file is named nginx.conf. The default directory is either /usr/local/nginx/conf, /etc/nginx, or /usr/local/etc/nginx.

You can find the exact location of the configuration file by entering nginx -V in a command line interface.

Update the server directive and add the proxy_set_header and proxy_pass directives in your configuration file. Use the following sample as a guide:

server {
    listen 443 ssl http2;

    ssl_certificate <path_to_certificate>;
    ssl_certificate_key <path_to_key>;

    server_name localhost;

    add_header Strict-Transport-Security max-age=31536000;

    location / {
        proxy_set_header X-Forwarded-Host $http_host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1;

        proxy_pass http://hubmachine.domain.local:1111;
    }
}

Set the following variables to match your Hub configuration:

• listen 443 is the port number that you specified in the --base-url parameter.

• proxy_pass http://hubmachine.domain.local:1111 is the path to your Hub server with the port that you specified with the -–listen-port command.

Save and close your configuration file.

Check for errors in your NGINX configuration by stopping and starting the server with the following commands:

sudo nginx -s stop
sudo nginx

Alternatively, you can reload the configuration with the following command:

sudo nginx -s reload

Use keytool to convert your current .jks file to the PKCS #12 key store format .p12:

keytool -importkeystore -srckeystore oldkeystore.jks -destkeystore newkeystore.p12 -deststoretype PKCS12
Enter destination keystore password: [enter private key password from oldkeystore.jks, it will be password for newkeystore.p12]
Re-enter new password: [same as above]
Enter source keystore password: [enter password for oldkeystore.jks]
...
Enter key password for <key alias name> [enter private key password from oldkeystore.jks]
...

You will be required to enter a destination keystore password. If your .jks keystore contains a private key with a password, then the destination keystore password should equal the password of the private key.

List the contents of the new keystore file:

keytool -deststoretype PKCS12 -keystore newkeystore.p12 -list
Enter keystore password: [enter password for newkeystore.p12 provided on step 1]
...

Extract the .pem file (certificate) from the .p12 keystore:

openssl pkcs12 -nokeys -in newkeystore.p12 -out certfile.pem
Enter Import Password: [enter password for newkeystore.p12 provided on step 1]
...

Extract the unencrypted key file from the .p12 keystore:

openssl pkcs12 -nocerts -nodes -in newkeystore.p12 -out keyfile.key
Enter Import Password: [enter password for newkeystore.p12 provided on step 1]
...