The Quick Connect dialog allows you to connect to a remote host that is not present in the session database.
Protocol
Select the protocol you want to use. SecureFX supports the following protocols:
SFTP
FTP
FTP/TLS
HTTP
HTTPS
SCP
Your choice of protocol will determine appearance of the FTP, SFTP/SCP , or HTTP/HTTPS group.
FTP group
The FTP group allows you to configure your FTP or FTP/TLS connection. This group only appears when FTP or FTP/TLS is selected as the Protocol.
Hostname or IP
Enter the hostname or IP address of the FTP server to which you want to connect. This is the only required field. After filling it in, you can click OK to make the connection.
Port
Enter the port number for the FTP server. The default FTP port is 21. The default FTP/TLS port is 990.
Firewall
If your connection involves a firewall, select your firewall from the list of firewalls that have been configured in the Global Options/Firewall dialog.
Note: You can also select an SSH2 session to be used as a firewall. When a session is specified as a firewall, the firewall session will be connected first.
Tip: This option may be useful for mobile customers that want to configure two different sessions to connect to the same server (one with and one without the firewall). One session can be used when at work (behind a firewall) and the other when traveling (connected directly to the Internet).
Anonymous login
When the Anonymous login option is selected, SecureFX automatically selects anonymous as the username and fills in the password field using the password you supplied in the Global Options/File Transfer/Options dialog. Unselecting this option makes the username and password fields available.
Username
Enter your username on the remote host.
Password
Enter your password.
SecureFX supports standard one-time password challenges and can generate responses using MD4 and MD5. It currently does not support S/Key and OPIE challenge formats. If the server issues a one-time password challenge, SecureFX will automatically calculate the required response using your password, prompting for it if necessary.
Note: If either the Username or Password entry box is left blank, then you will be prompted for that information when the connection is made.
Account
The account name to be used on the remote machine.
SFTP/SCP group
The SFTP/SCP group allows you to configure your SSH2 connection. This group only appears when SFTP or SCP is selected as the Protocol.
Hostname or IP
Enter the hostname or IP address of the remote SSH2 server. This is the only required field. After filling it in, you can click OK to make the connection.
Port
Enter the port number of the SSH2 server. The default port is 22.
Firewall
If your connection involves a firewall, select your firewall from the list of firewalls that have been configured in the Global Options/Firewall dialog.
Note: You can also select an SSH2 session to be used as a firewall. When a session is specified as a firewall, the firewall session will be connected first.
Tip: This option may be useful for mobile customers that want to configure two different sessions to connect to the same server (one with and one without the firewall). One session can be used when at work (behind a firewall) and the other when traveling (connected directly to the Internet).
Username
Enter your username on the SSH2 server.
Note: If the Username entry box is left blank, you will be prompted for that information when the connection is made.
Credentials
The set of credentials used to log on to the remote window. Press the Manage Saved Credentials button to add or edit saved credentials.
HTTP group
The HTTP group allows you to configure your HTTP or HTTPS connection. This group only appears when HTTP or HTTPS is selected as the Protocol.
Hostname or IP
Enter the hostname or IP address of the HTTP or HTTPS server to which you want to connect. This is the only required field. After filling it in, you can click OK to make the connection.
Port
Enter the port number for the HTTP or HTTPS server. The default HTTP port is 80. The default HTTPS port is 443.
Firewall
If your connection involves a firewall, select your firewall from the list of firewalls that have been configured in the Global Options/Firewall dialog.
Note: You can also select an SSH2 session to be used as a firewall. When a session is specified as a firewall, the firewall session will be connected first.
Tip: This option may be useful for mobile customers that want to configure two different sessions to connect to the same server (one with and one without the firewall). One session can be used when at work (behind a firewall) and the other when traveling (connected directly to the Internet).
Username
Enter your username on the remote host.
Password
Enter your password.
Authentication group
SecureFX supports several authentication methods for connecting to SSH2 servers, and will attempt to connect using them in the order that you specify.
Password authentication transmits the user's password to the server to authenticate the connection. The transmitted password is protected from network eavesdropping, due to the cipher encryption of the data channel.
PublicKey authentication uses a public/private key pair to authenticate the connection. During the authentication process, the client and the server negotiate a public key to use for the connection. Once a public key has been determined, the client uses the corresponding private key to perform a signature operation over a unique connection identifier. This signature is then sent to the server for verification. If verification is successful, the client is given permission to connect to the server. The security of the mechanism requires that no one but the owner have access to the private key. The private key is stored locally in an identity file. Also, prior to using public-key authentication, the public key must be made available to the SSH2 server.
Keyboard Interactive authentication allows you to use the keyboard to respond to challenges put forth by the server.
GSSAPI (Generic Security Services Application Program Interface) is a generic API for performing client/server authentication. GSSAPI allows SecureFX to authenticate with a server without knowing anything about the specific authentication mechanism in use. For more information about using GSSAPI, see GSSAPI Properties Dialog.
SecureFX also supports the use of X.509 certificates.
Properties
This button allows you to access the Properties dialog of the chosen authentication method.
Show quick connect on startup
Check this options to instruct SecureFX to display the Quick Connect dialog on startup. Press the Done button to save changes to this setting without making a connection.
Save session
Checking the Save Session check box will save the settings to the session database. The name used will be the hostname or IP address supplied for the session.
Click on the Connect button to complete your connection.