4.6

Table Of Contents
When the secure tunnel or PCoIP Secure Gateway is not enabled, the desktop session is established directly
between the client system and the View desktop virtual machine, bypassing the View Connection Server or
security server host. This type of connection is called a direct connection.
Clients that use the HP RGS display protocol do not use the tunnel connection or PCoIP Secure Gateway. These
clients must use direct connections.
IMPORTANT A typical network configuration that provides secure connections for external clients includes a
security server. To use View Administrator to enable or disable the secure tunnel and PCoIP Secure Gateway
on a security server, you must edit the View Connection Server instance that is paired with the security server.
In a network configuration in which external clients connect directly to a View Connection Server host, you
enable or disable the secure tunnel and PCoIP Secure Gateway by editing that View Connection Server instance
in View Administrator.
Procedure
1 In View Administrator, click View Configuration > Servers.
2 In the View Connection Servers panel, select a View Connection Server instance and click Edit.
3 Configure use of the secure tunnel.
Option Description
Disable the secure tunnel
Deselect Use secure tunnel connection to desktop.
Enable the secure tunnel
Select Use secure tunnel connection to desktop.
The secure tunnel is enabled by default.
4 Configure use of the PCoIP Secure Gateway.
Option Description
Enable the PCoIP Secure Gateway
Select Use PCoIP Secure Gateway for PCoIP connections to desktop
Disable the PCoIP secure Gateway
Deselect Use PCoIP Secure Gateway for PCoIP connections to desktop
The PCoIP Secure Gateway is disabled by default.
5 Click OK to save your changes.
Set a Single Sign-on Timeout Limit for View Users
By default, when a user logs in to View Connection Server from View Client, single sign-on (SSO) is enabled.
The user does not have to log in again to connect to the View desktop. During a desktop session, a user can
leave the desktop, allow it to become inactive, and return without having to authenticate again. To reduce the
chance that someone else could start using the desktop session, you can configure a time limit after which the
user's SSO credentials are no longer valid.
You configure the SSO timeout limit by setting a value in View LDAP. When you change View LDAP on a
View Connection Server instance, the change is propagated to all replicated View Connection Server instances.
The timeout limit is set in minutes. The time limit counter starts when the user logs in to View Connection
Server. For example, if you set the value to 10 minutes, the user's SSO credentials are invalidated 10 minutes
after the user logs in to View Connection Server.
NOTE On View desktops that are used in local mode, a checkout operation that takes longer than the SSO
timeout value causes the user's SSO credentials to expire. For example, you might set the SSO timeout limit to
10 minutes. A user might log in to View Connection Server and check out a desktop. If the checkout takes 20
minutes, the user must log in again to connect to the local desktop, even though the user has not yet spent any
time in a desktop session.
VMware View Administration
20 VMware, Inc.