Changes required for routing SFTP and HTTPS traffic through a SOCKS proxy
To use a SOCKS proxy to access email resources hosted by HCL, you must make changes to the web application where you have deployed Campaign and to the startup scripts for the Deliver RCT and RLU.
Making changes for SFTP
- Dhcl.unica.deliver.ftp.proxy.host = <socksHost>
- Dhcl.unica.deliver.ftp.proxy.port = <socksPort>
- Dhcl.unica.deliver.ftps.proxy.match.hosts = <comma separated list of host names and IP addresses>
socksHost is the host name or IP of the SOCKS proxy.
socksPort is the port on which SOCKS proxy is running.
-Dhcl.unica.deliver.ftps.proxy.match.hosts
matches host names
and IPs used when routing traffic through the SOCKS proxy.
The IP address specified for
-Dhcl.unica.deliver.ftps.proxy.match.hosts
is the IP address
that FTP seiver in the hosted OD environment sends to the FTP client in the
local OP environment as part of the SFTP protocol during data transfer.
Set -Dhcl.unica.deliver.ftps.proxy.match.hosts
to one of the
following values (depends on the data center used by your hosted email
account).
US data center:
-Dhcl.unica.deliver.ftps.proxy.match.hosts=ftp-em.unicadeliver.com
India data center:
-Dhcl.unica.deliver.ftps.proxy.match.hosts=ftp-in.unicadeliver.com
Europe data center:
-Dhcl.unica.deliver.ftps.proxy.match.hosts=ftp-eu.unicadeliver.com
Making changes for HTTPS
For HTTPS traffic, apply the following configurations to the RCT and the web application server.
-Dhcl.unica.deliver.https.proxy.host= <socksHost>
-Dhcl.unica.deliver.https.proxy.port= <socksPort>
-Dhcl.unica.deliver.https.proxy.type=SOCKS
socksHost is the host name or IP of the SOCKS proxy.
socksPort is the port on which SOCKS proxy is running.
Authentication requirements when using a SOCKS proxy
-Dhcl.unica.deliver.proxy.auth.user = <username>
-Dhcl.unica.deliver.proxy.auth.password = <password>
Where username and password are the credentials required to authenticate against the proxy.