Sentinel: How to configure Advisor behind a Proxy server

Advisor configuration needs to be updated to be able to connect to the Advisor server through a proxy server for feed downloads. This could involve adding up to 4 new properties to each "container.xml” file that Advisor uses. If the proxy server does not require authentication, we just need to add the proxy server’s host and port information. If it requires authentication, we need two additional properties – username and password for the proxy server. (Currently, we only support BasicAuthentication. Supporting DigestAuthentication will require code changes)

1. Install Advisor in "Direct Connection” mode. Since the current installer does not support connection through a proxy server, the authentication check done by the installer will fail, but continue with the installation anyway.

2. cd to %ESEC_HOME%\sentinel\config

3. Edit alertcontainer.xml and add the following lines to the section named"DownloadComponent”

proxy_host">proxyHost

proxy_port">proxyPort

If the proxy server requires authentication, also add the following properties after the above properties

proxy_username">proxyUser

proxy_password" />

(Replace proxyHost, proxyPort etc with the actual values)

4. Repeat step 3 for attackcontainer.xml.

5. If the proxy server does not require authentication, go to step 9.

6. Download proxy_passwd_update file

7. Copy the fileproxy_passwd_update.batto %ESEC_HOME%\sentinel\bin

8. cd to %ESEC_HOME%\sentinel\config and run this tool to update the Advisor container files with the proxy user password.

"%ESEC_HOME%\sentinel\bin\proxy_passwd_update.bat” proxyPasswd

where proxyPasswd is the proxy password for the user

9. Verify that alertcontainer.xml and attackcontainer.xml now contain the encrypted proxy password.

10. Run advisor.bat to download and process Advisor data.

11. Monitor %ESEC_HOME%\sentinel\log\Advisor_0.0.log and %ESEC_HOME%\sentinel\log\advisor.log to verify that Advisor can connect through the proxy server.