When no proxy authentication is needed, omit the user:
Test the connection to GTI with the following
commands:
curl -kvx proxyaddress:port https://tie.repl.gti.trellix.com:443
NOTE: In the TIE Server 4.0 and later versions, the URL used for reputation lookups has changed. Use the following command:
curl -x proxyaddress:port -kv -X POST -H "Content-Type:application/json; charset=utf-8" https://tieserver.rest.gti.trellix.com/1
Example:
curl -kvx 192.168.2.100:8080 https://tie.repl.gti.trellix.com:443
IMPORTANT: The URL
tieserver.rest.gti.trellix.com was introduced in TIE Server 4.0, so make sure it has been
added to the allow list in your proxy configuration.
If the test is successful, a message with a connection using port 443 is displayed with no errors.
The following are examples of the expected response if the proxy connectivity is successful and depending on the URL used:
Example 1
(tie.repl.gti.trellix.com:443):
[…]
* Establish HTTP proxy tunnel to tie.repl.gti.trellix.com:443
> CONNECT tie.repl.gti.trellix.com:443 HTTP/1.1
> Host: tie.repl.gti.trellix.com:443
[…]
< HTTP/1.1 200 Connection established
[…]
* issuer: C=US,O=SCC,CN=TrustedSource_CA
[…]
> Accept: */*
Example 2
(tieserver.rest.gti.trellix.com:443):
[…]
* Establish HTTP proxy tunnel to tieserver.rest.gti.trellix.com:443
> CONNECT tieserver.rest.gti.trellix.com:443 HTTP/1.1
> Host: tieserver.rest.gti.trellix.com:443
[…]
* issuer: C=US; ST=CA; L=Santa Clara; O=McAfee, Inc.; CN=McAfee OV SSL CA 2
[…]
> Accept: */*
If the issuer parameter doesn't match, the proxy or another networking device might be trying to replace the certificate and inspect content at the secured communication. Either disable this option or enable a proxy exclusion to allow the TIE Server to establish a secured connection to the GTI device. Also, look at what type of proxy authentication is needed for your environment.
