In some highly secured environments, you may be required to enabled HTTP Strict Transport Security (HSTS) on the VM Access Proxy, to add an additional layer of security to remote connections. Follow the process  below to enable on the VM Access Proxy. 

Important! This configuration will not currently survive an upgrade of the VM Access Proxy, as the entire container for the application is replaced during upgrades, and HSTS support (or being enabled by default) is not yet available. 

1. Login to the VM Access Proxy.
2. SSH into the container itself by issuing the command: 

sudo docker exec -it remoteaccess /bin/bash

2. The container image is very lightweight, so next install the vim text editor :
   • Issue the command:

apt-get update

• Issue the command: 

apt-get -y install vim

3. Issue the command below to edit the tomcat webserver web.xml configuration file:

vim tomcat/webapps/RemoteAccess/WEB-INF/web.xml

4. Add the following contents before the </web-app> tag:

<filter> 
	<filter-name>httpHeaderSecurity</filter-name> 
    <filter-class>org.apache.catalina.filters.HttpHeaderSecurityFilter</filter-class> 
    <async-supported>true</async-supported> 
	<init-param> 
		<param-name>hstsEnabled</param-name> 
		<param-value>true</param-value> 
	</init-param> 
	<init-param>
		<param-name>hstsMaxAgeSeconds</param-name>
		<param-value>31536000</param-value> 
	</init-param> 
	<init-param> 
		<param-name>hstsIncludeSubDomains</param-name> 
		<param-value>true</param-value> 
	</init-param> 
</filter> 

<!-- The mapping for the HTTP header security Filter --> 

<filter-mapping> 
	<filter-name>httpHeaderSecurity</filter-name> 
	<url-pattern>/*</url-pattern> 
	<dispatcher>REQUEST</dispatcher> 
</filter-mapping>

5. Hit [ESC] and then enter :wq to save your changes. See the attached example file for your reference.
6. Logout of the container by issuing the command: 

exit

7. Issue the following command to restart the container: 

docker restart remoteaccess

8. Scan with security software to confirm that the configuration has succeeded. Alternatively, ping the VM Access Proxy using postman to verify that it responds with the HSTS header present. 
9. Login to Commander and confirm that connections are successful.