Configuring a Client SSL Connection

You must configure a client to use an SSL connection within the client's host access configuration. For example, there are two basic types of SSL connections that you can set in a viewer configuration:

The remainder of the topic describes these two connection scenarios.

Note Depending on your host's SSL configuration, you may have to install personal certificates on client PCs. For instructions, see Installing a Personal Certificate.

Direct Connection to a Host

As shown in the diagram below, a client and host configured for SSL communicate over a secure Telnet session. To configure a host for SSL, see the host security documentation.

Connection to a Host via Security Services

As shown in the diagram below, this option allows you to secure client connections over the Internet to hosts that are not enabled for SSL. Outside of the firewall, MCS passes secured host traffic over the Internet; inside the firewall, MCS forwards the traffic unencrypted to the hosts.

The inbound (client to MCS) side of the connection requires only a single HTTPS port, thereby minimizing the impact on both the client-side and server-side firewall security policies. The outbound (MCS to host) side of the connection provides a destination filter that restricts access to only authorized host addresses and ports.

The Attachmate-supplied default allows for unrestricted access to hosts. To set up an authorized list of hosts, you must modify the SecurityGateway.properties file. For instructions, see Limiting Access to Authorized Hosts.

Related Topics
Bullet Security Services, Overview
Bullet SSL Certificates
Bullet Configuring Security Services
Bullet Installing a Personal Certificate
Bullet Limiting Access to Authorized Hosts
  Attachmate