FTP Proxy Service
The FTP Proxy Service provides connectivity for FTP client applications that support the username@hostname method of firewall traversal. This includes the common Windows command-line FTP client, and other common FTP applications such as Filezilla, and CuteFTP.
Setting
|
Default value
|
Service Port
|
21
|
Bindings
|
The FTP Proxy Service will automatically bind to any network interfaces that have their usage marked as Internal by WinGate.
|
Registered events
|
ClientConnect, ClientDisconnect, ConnectToServer
|
Require auth to proxy
This setting on the General tab of the FTP Proxy Service properties, will force clients who have their FTP applications set to use a proxy, to authenticate themselves with the FTP Proxy before being given connection access to the remote FTP server. This authentication requires the valid credentials of a user in the user database that has been selected by WinGate.
Rather then enabling this setting on the FTP Proxy service itself, the Require auth to proxy option can be set per client connection when using any WinGate event processor to process the ClientConnect event registered by the FTP Proxy service.
Using the Symbol Browser to access registered WinGate objects, you can use the RequireAuth boolean (provided by the Session object) to control if Proxy auth is required. This is useful when you want other conditions surrounding the ClientConnect event to be evaluated before deciding if auth to the proxy is needed.
e.g. A script could contain
Session.RequireAuth(true)
This would force the user to authenticate themselves with the FTP Proxy service, before their actual FTP connection can proceed.
Note
The Require auth to Proxy option is only available to clients who have their FTP client software configured to use the WinGate FTP Proxy service. This option will not available for clients who are making FTP connections that are being intercepted by the FTP Proxy service.