8.4.3 Connect using End-to-End Encryption in VT SSH Sessions

You can configure a Reflection Desktop session to send an SSH-encrypted connection through the Security Proxy Server.

In a standard Administrative Console configuration for a secure Reflection session, the connection between the client and security proxy server is encrypted using SSL/TLS, but the connection between the security proxy and the host uses unencrypted Telnet. By sending an SSH-encrypted connection through the security proxy tunnel, you can configure a secure Reflection session so that the entire communication path is encrypted from the client, through the proxy server, and on to the host.This feature has the following advantages:

  • Encryption is used for the entire connection.

  • The IP addresses and names of your secure hosts are not exposed outside of the internal network.

  • Only clients with a valid authorization token can launch a secure session.

  • The authorization token contains connection information. This enables the security proxy to send all secure host connections through a single port, eliminating the need to open multiple firewall ports.

  • All settings required for a connection (such as the trusted certificate, the personal certificate, user keys, and host keys) reside on the Administrative Console and are downloaded to users’ workstations when they start sessions.

You can set up this configuration using the Reflection VT Terminal type (used for UNIX and OpenVMS sessions).

To connect your VT session SSH connection through the Security Proxy Add-On

  1. Follow the instructions for creating a new session in the Management and Security Server Administrator Guide in the Host Access Management and Security Server Documentation to create a new VT session.

  2. When you configure the session, select Secure Shell for the connection type.

  3. Enter the host name and user name (optional; users are otherwise prompted when they connect). Then select Configure additional settingsand click OK to open the Settings dialog box.

  4. Under Host Connection, click Set up Connection Security.

  5. In the Reflection Secure Shell Settings dialog box, on the Reflection Security Proxy tab, select Use Security Proxy, and then choose a Security proxy and a Proxy port.

    NOTE:The Destination host values you entered in step 6 should be entered automatically here. If you don't see them, select the Security proxy name from the drop-down list to populate these fields.

  6. Configure SSH connection settings such as the trusted certificate, the personal certificate, user keys, and host keys as required for your connection. For more information about configuring your SSH-specific settings, refer to the Reflection Help topic Reflection Secure Shell Settings Dialog Box.

  7. Click OK to close the open dialog boxes and initiate the connection. Select Always to import the host key for these sessions.

    NOTE:If you do not want to include the user name in the configuration, cancel the connection. If you cancel, you will be unable to import the host key for the session.

  8. Save the session. When prompted, choose to send the settings for this session to the Administrative Console, and then exit the Reflection workspace.

    All the files required for your configuration are uploaded to the Administrative Console. When a user launches the session, these files are downloaded to their workstation so that Reflection has access to all configuration data required to establish a connection.

NOTE:All non-default SSH settings required to establish a connection are saved in three files:

  • The sessionname.rssh file contains the public key (if public key authorization is used), the host key (if a host key is accepted while in administrative mode), and the settings normally stored in both the pki_config file and the config file. It also includes all SSL/TLS settings such as the TLS version, cipher suites, and applicable proxy data.

  • The sessionname.ps file stores any personal certificates included for the connection.

  • The sessionname.ts file includes any trust certificates.

When you send settings for the session to the Administrative Console, these files are uploaded along with the session document file.