The FastX Desktop Client offers multiple connection methods depending on your system’s set up. Both methods have their advantages and it is important to weigh the requirements of your organization when making a choice.
The SSH Connection Method
The SSH Connection Method offers an industry standard way to connect to the FastX Server. Authentication is done through standard SSH practices. All modern SSH authentication methods (Public Key, Challenge Response, Dual Factor, Kerberos etc) are supported. Traffic is encrypted through the SSH channel and runs over port 22 (by default). The SSH Connection Method offers piece of mind to network administrators and is convenient to implement.
The Web Connection Method
The web connection runs over HTTP/HTTPS and Websockets. The web connection method offers extra features not available in the SSH Connection method.
Advanced Authentication Methods
The FastX Web Connection uses SSH to authenticate by default. The client communicates to an ssh client on the server side and makes a proxy connection over the web for initial authentication. The Web Connection’s SSH module can authenticate via most SSH authentication methods. Kerberos is not supported,
Many customers have moved to Single Sign On authentication, or other methods. Any authentication method which is not SSH must use the Web Connection
The SSH connection method always connects to the same system as defined by the hostname. The web connection has the ability to choose the final destination for you and route your connection so you can load balance your systems