Technical Notes |
|
This technical note explains how to configure Reflection for the Web to provide end-to-end encryption by tunneling an SSL/TLS direct connection to the host through a security proxy.
This document is presented in the following sections:
In a standard configuration of secure Reflection for the Web sessions, 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. In some network environments it is necessary to have the entire communication path encrypted, from the client, through the proxy server, and to the host.
Figure 1 Security Proxy Session vs. End-to-End EncryptionStarting in Reflection for the Web 8.5, Reflection can be configured for end-to-end encryption with token authorization. This feature enables the client to use SSL encryption to connect to the proxy and host securely, through an SSL tunnel. This feature has the following advantages:
In versions earlier than 8.5, Reflection for the Web used the security proxy's pass-through mode to provide end to end encryption. Because pass-through mode does not support token authorization, this configuration required that multiple ports be opened in the firewall. For further details, see the Proxies tab of the Security Proxy Wizard in the online help.
Two certificates and SSL handshakes are involved in each end-to-end encryption connection, one between the client and proxy server, and one between the client and host. Before enabling end-to-end encryption in Reflection for the Web you must configure Reflection for the Security Proxy Certificate and the Host Certificate.
The Reflection for the Web security proxy must be installed and configured. Once the security proxy configuration is complete, the security proxy certificate is created and imported into the Reflection Management Server.
For further details about installing the security proxy, see the Reflection for the Web Installation Guide:
Reflection for the Web 2008: http://support.attachmate.com/manuals/rweb2008.html
Reflection for the Web 9.6: http://support.attachmate.com/manuals/wthdocs.html
For information about configuring the security proxy when doing a manual installation, see Technical Note 1812.
Once the security proxy configuration is complete, follow the steps below to
To configure your systems so that the SSL handshake between the client and host is successful, you must do one of the following:
When creating the host certificate, list the host name of the proxy server as a subject alternate name (recommended).
Server identity verification can be disabled globally (for all Reflection sessions), or per session.
Globally:
To globally disable server identity verification, follow these steps:
Per Session:
To disable server identity verification for a single session, follow these steps:
Note: If you do not plan to disable server verification, you must modify your host certificate with a subject alternate name before you complete the import. The subject alternative name must match the server name used for the security proxy.
Enable SSL on the host. For details, refer to your host documentation.
Follow the steps below to import the host certificate into Reflection:
For more details on configuring SSL and creating certificates on the host, see Technical Notes 1759 and 1760.
Follow these steps to enable end-to-end encryption.