Administration

Table Of Contents
When the Blast Secure Gateway is not enabled, client devices and client Web browsers use the VMware Blast
Extreme protocol to establish direct connections to remote desktop virtual machines and applications,
bypassing the Blast Secure Gateway.
I A typical network conguration that provides secure connections for external users includes a
security server. To enable or disable the Blast Secure Gateway on a security server, you must edit the
Connection Server instance that is paired with the security server. If external users connect directly to a
Connection Server host, you enable or disable the Blast Secure Gateway by editing that Connection Server
instance.
Prerequisites
If users select remote desktops by using VMware Identity Manager, verify that VMware Identity Manager is
installed and congured for use with Connection Server and that Connection Server is paired with a SAML
2.0 Authentication server.
Procedure
1 In Horizon Administrator, select View  > Servers.
2 On the Connection Servers tab, select a Connection Server instance and click Edit.
3 Congure use of the Blast Secure Gateway.
Option Description
Enable the Blast Secure Gateway
Select Use Blast Secure Gateway for Blast connections to machine
Disable the Blast secure Gateway
Deselect Use Blast Secure Gateway for Blast connections to machine
The Blast Secure Gateway is enabled by default.
4 Click OK to save your changes.
Off-load SSL Connections to Intermediate Servers
Horizon Client must use HTTPS to connect to View. If your Horizon clients connect to load balancers or
other intermediate servers that pass on the connections to View Connection Server instances or security
servers, you can o-load SSL to the intermediate servers.
Import SSL Off-loading Servers' Certificates to View Servers
If you o-load SSL connections to an intermediate server, you must import the intermediate server's
certicate onto the View Connection Server instances or security servers that connect to the intermediate
server. The same SSL server certicate must reside on both the o-loading intermediate server and each o-
loaded View server that connects to the intermediate server.
If you deploy security servers, the intermediate server and the security servers that connect to it must have
the same SSL certicate. You do not have to install the same SSL certicate on View Connection Server
instances that are paired to the security servers and do not connect directly to the intermediate server.
If you do not deploy security servers, or if you have a mixed network environment with some security
servers and some external-facing View Connection Server instances, the intermediate server and any View
Connection Server instances that connect to it must have the same SSL certicate.
If the intermediate server's certicate is not installed on the View Connection Server instance or security
server, clients cannot validate their connections to View. In this situation, the certicate thumbprint sent by
the View server does not match the certicate on the intermediate server to which Horizon Client connects.
Chapter 2 Configuring View Connection Server
VMware, Inc. 35