Set Up SSH for QAD .NET UI
To support the character screens, you can use SSH rather than standard telnet. SSH (or Secure SHell) is a protocol for creating a secure connection between a QAD .NET UI client and the server. The safeguards provided by SSH include:
• User authentication and key exchange.
• Negotiate encryption, compression, and message integrity verification.
• All data is encrypted using a sysmetric key algorithm and verified against a keyed-hash message authentication code (HMAC).
Note: If SSH is enabled for QAD .NET UI, you will not be able to use telnet for Desktop sessions because the Desktop UI does not support SSH. You can separate telnet and SSH users by creating settings in User Option Telnet Maintenance.
To set up SSH, follow these steps:
1 Download granados200.tar.gz from the following link to a temporary directory:
Note: This file is not included with QAD software because of exportation laws regarding encryption.
2 Extract Routrek.granados.dll from the archive using gunzip and tar. You must use version 2.0.0.0 of the DLL signed by Routrek Networks or SSH will not work.
The gunzip and tar programs are UNIX utilities. The commands follow. Some WinZip versions support *.tar.gz files.
a Create granados200.tar:
gunzip granados200.tar.gz
b Extract the tar archive:
tar -xf granados200.tar
The DLL file will be located in the temporary directory’s /bin directory.
3 Copy the DLL to TomcatInstallDir/webapps/qadhome. This is the default location.
4 Open qaduiConfig.xml in TomcatInstallDir/webapps/ qadhome/client/configs where qaduiConfig is your QAD UI configuration name.
The client session file defines client session characteristics of the QAD .NET UI. By default, the file is located in TomcatInstallDir/webapps/qadhome/configurations/ default/client-session.xml. In the following step, the elements you must edit in client-session.xml include <SshProviderUrl> and <TerminalProtocol>.
5 Make the following changes:
a Update the location of the DLL file:
<add key="SshProviderUrl" value="${HomeServer}/ Routrek.granados.dll" />
${HomeServer} is automatically replaced with the HomeServer configuration value defined at installation time. All ${<variable>} references are resolved against other configuration keys. If no key is found, then the string is not replaced.
b Change the terminal protocol entry from telnet to either SSH1 or SSH2. SSH2 is preferred because it is more secure.
<add key="TerminalProtocol" value="SSH2" />
6 Save the configuration file.
7 Repeat these steps for default.xml in the same directory.
8 In User Option Telnet Maintenance (36.20.10.3), change the port from 23 to 22. This is the default port for SSH.