SSL/TLS Tab (Security Properties Dialog Box)
Getting there (Reflection)
- Open the Document Settings dialog box.
The steps depend on your user interface mode.
User Interface Mode
|
Steps
|
Ribbon or Reflection Browser
|
With a session open in Reflection, from the Quick Access Toolbar, click .
|
TouchUx
|
Tap the Gear icon and then select Document Settings.
|
- Under Host Connection, click Setup Connection Security.
- (3270 and 5250 terminal sessions only) Under Security, click Security Settings.
Getting there (FTP Client)
- In the Connect to FTP Site dialog box, select a site.
- Click Security.
The Secure Sockets Layer protocol (SSL) and its compatible successor, the Transport Layer Security protocol (TLS), enable a client and server to establish a secure, encrypted connection over a public network. When you connect using SSL/TLS, the client authenticates the server before making a connection, and all data passed between Reflection and the server is encrypted. Depending on the server configuration, the server may also authenticate the client.
The options are:
|
Use SSL/TLS Security
|
Enables SSL/TLS connections. You must select this before you can set other values on the SSL/TLS tab. When Use SSL/TLS security is selected, Reflection will only connect to the host if a secure SSL/TLS connection can be established.
Before making an SSL/TLS connection, Reflection must authenticate the host. Authentication is handled through the use of digital certificates. These certificates are part of the same Public Key Infrastructure (PKI) that is used to secure internet transactions. Your computer must be configured to recognize the digital certificate presented by your host and, if necessary, to provide a certificate for client authentication. If your computer is not properly configured, or if the certificates presented for authentication are not valid, you will not be able to make SSL/TLS connections. Depending on how a host certificate was issued, you may need to install a certificate on your local computer.
|
|
Configure PKI
|
Opens the PKI Configuration dialog box, which you can use to configure PKI settings for Reflection SSL/TLS sessions.
|
|
Encryption Strength
|
Specify the desired level of encryption for SSL/TLS connections. The connection will fail if this level cannot be provided.
If you select Default, any encryption level is permitted, and Reflection will negotiate with the host system to choose the strongest encryption level supported by both the host and the client. If you are running in FIPS mode and select Default, Reflection will negotiate using only FIPS compliant encryption levels.
|
|
SSL/TLS version
|
Specifies which SSL or TLS version to use.
|
|
Retrieve and validate certificate chain
|
Specifies whether certificates presented for host authentication are checked to determine if they are valid and signed by a trusted CA. Note: Certificate validation is required when SSL/TLS version is set to TLS version 1.0 or TLS version 1.2. To clear this setting (which disables certificate validation), you must set SSL/TLS version to SSL Version 3.0.
Caution: Clearing this setting creates a security risk by allowing host authentication with unvalidated certificates.
|
Reflection Security Proxy Server Settings
Use Reflection security proxy and related settings are visible if you use Reflection Security Gateway (available separately from Attachmate) to manage sessions and you launched this session from the Administrative WebStation. With these options, Reflection connects to your host via the Reflection Security Proxy included in Reflection Security Gateway. You can use this Security Proxy to configure secure connections even if your host is not running an SSL/TLS-enabled Telnet server.
Notes
- When the Security Proxy is used, the connection between the client and the Security Proxy server is secured and encrypted using the SSL/TLS protocol. By default, the information sent between the proxy server and the destination host is in the clear. If you enable the End-to-End encryption option (available for 5250, 3270, and VT sessions), information sent between the Security Proxy the destination host is also encrypted. (End-to-End encryption requires that the host support SSL/TLS.)
- If you configure sessions that connect through the Security Proxy with authorization enabled, users must log onto the Reflection Security Gateway server before they can connect using these sessions.
|
Use Reflection security proxy
|
Configure this session to use the Reflection Security Proxy for the server connection.
|
|
Security proxy
|
Select the proxy server name from the drop-down list shows, which shows available servers.
|
|
Proxy port
|
Select the proxy server port from the drop-down list.
|
|
Destination host
|
If client authorization is enabled on the Security Proxy, enter the destination host name. If client authorization is not enabled, this box is read only.
When you select a security port, the destination host configured to use that port is displayed automatically.
|
|
Destination port
|
If client authorization is enabled on the Security Proxy, enter the destination host name. If client authorization is not enabled, this box is read only.
When you select a security port, the destination port and destination host are displayed automatically.
|
|
End-to-End encryption
|
This option tunnels a direct SSL/TLS connection to the host, while still connecting through the Reflection Security Proxy Server. These connections require two certificates and two SSL/TLS handshakes—one for the client/proxy server connection and another for the client/host connection.
|
|
Proxy cipher suites
|
A read-only list of cipher suites supported by this Reflection proxy host and port. This list is only visible when the product is launched from the Administrative WebStation (included with Reflection Security Gateway).
|
|