5.2

Table 1-4. Global Security Settings for Client Sessions and Connections
Setting Description
Reauthenticate secure tunnel connections after
network interruption
Determines if user credentials must be reauthenticated after a network
interruption when View clients use secure tunnel connections to View
desktops.
When you select this setting, if a secure tunnel connection ends during
a desktop session, View Client requires the user to reauthenticate before
reconnecting.
This setting offers increased security. For example, if a laptop is stolen
and moved to a different network, the user cannot automatically gain
access to the remote desktop because the network connection was
temporarily interrupted.
When this setting is not selected, the client reconnects to the desktop
without requiring the user to reauthenticate.
This setting has no effect when you use direct connection.
Message security mode Determines if signing and verification of the JMS messages passed
between View Manager components takes place. For details, see
“Message Security Mode for View Components,” on page 30.
By default, message security mode is enabled.
Use IPSec for Security Server connections Determines whether to use Internet Protocol Security (IPSec) for
connections between security servers and View Connection Server
instances.
By default, secure connections (using IPSec) for security server
connections is enabled.
Disable Single Sign-on for Local Mode
operations
Determines if single sign-on is enabled when users log in to their local
desktops.
If you enable this setting, users must manually log in to their desktops
to start their Windows sessions after they log in.
When you change this setting, the change takes effect for each user at
the next user operation.
NOTE If you upgrade to View 5.1 or later from an earlier View release, the global setting Require SSL for
client connections is displayed in View Administrator, but only if the setting was disabled in your View
configuration before you upgraded. Because SSL is required for all View Client connections and View
Administrator connections to View, this setting is not displayed in fresh installations of View 5.1 or later
versions and is not displayed after an upgrade if the setting was already enabled in the previous View
configuration.
After an upgrade, if you do not enable the Require SSL for client connections setting, HTTPS connections
from View clients will fail, unless they connect to an intermediate device that is configured to make onward
connections using HTTP. See “Off-load SSL Connections to Intermediate Servers,” on page 33.
Message Security Mode for View Components
You can set message security mode for View components. This setting determines how sender signatures in
JMS messages are treated. By default, JMS messages are rejected if the signature is missing or invalid, or if a
message was modified after it was signed.
If any component in your View environment predates View Manager 3.0, when message security was
introduced, you can change the mode to log a warning if any of these conditions are found, or to not verify
signatures at all. These options are not recommended and it is preferable to upgrade older components.
Some
JMS messages are encrypted because they carry sensitive information such as user credentials. Consider
using IPSec to encrypt all JMS messages between View Connection Server instances, and between View
Connection Server instances and security servers.
VMware Horizon View Administration
30 VMware, Inc.