Set Up SSH
For terminal mode display, you can use SSH (Secure Shell) rather than standard telnet. SSH is a protocol that can create a secure connection between a QAD .NET UI client and the server.
The safeguards that SSH provides include:
• User authentication and key exchange
• Negotiated encryption, compression, and message integrity verification
• All data is encrypted using a symmetric key algorithm and verified against a keyed-hash message authentication code (HMAC).
To set up SSH, follow these steps:
1 If you installed QAD EE 2013, go directly to step
2. If you upgraded from QAD EE 2012.1 or earlier to the latest EE version, do the following:
a Back up the existing $TOMCAT/webapps/$QADUI/WEB-INF/conf
/connectionManagerConfig.xml file.
b Copy the template $TOMCAT/webapps/$QADUI/WEB-INF/conf/defaults
/connectionManagerConfig.xml to $TOMCAT/webapps/$QADUI/WEB-INF/conf/connectionManagerConfig.xml.
c Edit the new connectionManagerConfig.xml in the QAD UI: Administration - Connection Manager screen.
2 Download granados200.tar.gz from the following link to a temporary directory:
Note: This file is not included with QAD software because of encryption export control laws.
3 Extract Routrek.granados.dll from the archive using gunzip and tar. Use version 2.0.0.0 of the DLL signed by Routrek Networks. Otherwise, SSH does not work.
The gunzip and tar programs are Linux/UNIX utilities. 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 is located in the temporary directory’s /bin directory.
4 Copy the DLL to <tomcat_install_directory>/webapps/<qadhome>. This path is the default location.
5 Open <qaduiConfig>.xml in <tomcat_install_directory>/webapps/ <qadhome>/client/configs where <qaduiConfig> is your QAD UI configuration name.
Note: The client session file defines the client session characteristics of the QAD .NET UI. By default, the file is located in:
<tomcat_install_directory>/webapps/<qadhome>/configurations/default/client-session.xml
In the following step, the elements you must edit in client-session.xml include <ssh_provider_url> and <terminal_protocol>.
6 Make the following changes:
a Update the DLL file location:
<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 a key is not found, the string is not replaced.
b Change the terminal protocol entry from telnet to SSH1 or SSH2 (SSH2 is preferred because it is more secure):
<add key="TerminalProtocol" value="SSH2" />
7 Save the configuration file.
8 Repeat these steps for default.xml in the same directory.
9 In User Option Telnet Maintenance (36.4.14), change the port from 23 to 22. This value is the default port for SSH.