Apache Proxy to ESET Bridge Migration Confusion

[GDI 1]

Maybe I'm being dense, but I'm not quite understanding the migration instructions from Apache HTTP Proxy to ESET Bridge. We are using Protect On-Prem on Windows Server 2019.

I've read the instructions at https://help.eset.com/ebe/1/en-US/migrate_from_http_proxy.html and have the following questions:

1. First, the warning says "Do not install ESET Bridge on the computer running Apache HTTP Proxy" then it says that if I run the all-in-one installer, it'll uninstall Apache HTTP proxy and install ESET Bridge. Seems like those instructions are contradictory. Should I run the all-in-one installer on the ESET protect server to replace Apache HTTP Proxy with ESET bridge?

2. Step 2 says to configure the ESET Bridge Policy, but the "Install ESET Bridge" instructions says it creates the default HTTP Proxy Usage policies. So, which one is it? Do I create new policies or does the ESET Bridge installation create the policies?

Thanks!

[IggyPop 16]

Hi @GDI,

Thanks for reaching out to us I will try to answer to all your questions which you have.

1. First of all the ESET Bridge is recommended to be installed after uninstalling the Apache Proxy as the all-in-one does not replace the Apache Proxy.
2. The default policy allows HTTP, however, afterwards you can create policy via ESET PROTECT for HTTPS in case you would like to utilize the HTTPS for your environment and some other configurations such as authentication and etc. For this I would recommend checking out this https://help.eset.com/ebe/1/en-US/migrate_from_http_proxy.html?agent_policy.html.

Hope it helps,

Thanks!

Ingemar 

[GDI 1]

6 hours ago, IggyPop said:

First of all the ESET Bridge is recommended to be installed after uninstalling the Apache Proxy as the all-in-one does not replace the Apache Proxy.

Thank you for the info! Regarding the info I quoted above, I'm still a bit confused. I copied our current ESET installation to a test server and ran the all-in-one installer. Once the installer opened, it had an option to install ESET Bridge, so I went ahead and tried it out and it did in fact uninstall the Apache HTTP Proxy. I confirmed this because before I started the installer, we had a "ApachHttpProxy" service. After the all-in-one installer ran and I restarted the server, the "ApachHttpProxy" service was no longer there and the "ESET Bridge" service was installed.

Edited March 3 by GDI

[IggyPop 16]

Hi @GDI,

this is possible, however, officially we aren't supporting this yet. We are making some improvements in the next version of the ESET Bridge so stay tunned.

Thanks for the investigation tho.

Ingemar