|
Configuring View Security Server |
|
|
|
|
Written by Tom Hirt
|
|
Thursday, 26 February 2009 16:07 |
|
Page 1 of 5 VMware's View Manager Security server is a component of the View architecture which provides secure access to VMware View sessions over an unsecured WAN and/or Internet. Use of the Security server allows protection to the connection broker from the public Internet while also creating a secure mechanism for remote users to access the View environment. For deployments where two-factor authentication is desired, the Security Servers can also be configured with RSA SecurID integration.
The Security server basically acts like a proxy to securely connect outside hosts to the trusted inside network. In a typical deployment, the Security server(s) is placed in the DMZ. Although not required, it is best practice to deploy two Security servers, a Standard Security server and a Replica Security server, for a fault tolerant configuration. When using a fault tolerant configuration, a 3rd party load balancer must also be deployed to manage connection state and fail-over between the Standard and Replica servers.
The following diagram illustrates the components for deployment:

As a prerequisite for deployment, one or more View Manager Connection servers must be present and configured with their associated dependencies satisfied (Active Directory, Virtual Center and an ESX host/cluster deployed). Please see our knowledge base for further details on the configuration of these dependencies.
Because the Security servers only offer a small subset of the features offered by the View Connection server, there is no need for the Security server to have or be a part of the Active Directory domain. Further more, these servers do not contain LDAP schemas or other repositories for Active Directory or RSA Authentication Manager (if deployed with two-factor authentication) enforcing a strong security posture that is protected from possible compromise.
|
|
Last Updated on Tuesday, 02 June 2009 11:12 |