Configuring Virtual Host Settings

Creating a virtual host allows users to log in using a different hostname than your default URL. For example, sales members can access https://sales.company.com instead of the default domain, https://vpn.company.com that you use for administration. The Portal URL (for example, https://vpn.company.com/portal/sales) will still exist even if you define a virtual host name. Virtual host names enable administrators to give separate and distinct login URLs to different groups of users.

To create a Virtual Host Domain Name:

Navigate to Portals > Portals.

Click the Add Portal button or the configure button next to the portal you want to configure. The Add Portal or Edit Portal screen displays.

Click the Virtual Host tab.

Enter a host name in the Virtual Host Domain Name field, for example, sales.company.com. This field is optional.

Only alphanumeric characters, hyphen (-) and underscore (_) are accepted in the Virtual Host Name/Domain Name field.

Select a specific Virtual Host Interface for this portal if using IP based virtual hosting.

If your virtual host implementation uses name based virtual hosts — where more than one hostname resides behind a single IP address — choose All Interfaces from the Virtual Host interface.

If you selected a specific Virtual Host Interface for this portal, enter the desired Virtual Host IP Address in the field provided. This is the IP address users will access in order to access the Virtual Office portal.


	NOTE: Be sure to add an entry in your external DNS server to resolve the virtual hostname and domain name to the external IP address of your SRA appliance.

If you selected a specific Virtual Host Interface for this portal, you can specify an IPv6 address in the Virtual Host IPv6 Address field. You can use this address to access the virtual host. Enter the IPv6 address using decimal or hexadecimal numbers in the form:

2001::A987:2:3:4321

If you plan to use a unique security certificate for this sub-domain, select the corresponding port interface address from the Virtual Host Certificate list.

Unless you have a certificate for each virtual host domain name, or if you have purchased a *.domain SSL certificate, your users may see a Certificate host name mismatch warning when they log into the SRA appliance portal. The certificate hostname mismatch affects the login page, NetExtender, and Secure Virtual Access/Assist/Meeting clients; Other SRA client applications will not be affected by a hostname mismatch.

To achieve a single point of access for users, configure External Website Bookmarks for application offloading portals by selecting the Enable Virtual Host Domain SSO check box to enable cross domain Single Sign-On (SSO). Cross Domain SSO shares the credentials for all portals in the same shared domain. Enabling Virtual Host Domain SSO automatically sets the Shared Domain Name one level up from the Virtual Host Domain name and displays it in the Shared Domain Name field. For example, the Shared Domain Name is example.com if the Virtual Host Domain is webmail.example.com.


	NOTE: In previous releases, users had to log in twice – once for the regular portal and once for the application offloading portal after External Website Bookmark redirection. The Cross Domain SSO feature allows users after logging into the main portal to automatically log into application offloading portals or Web sites that share the same Virtual Host Domain.

Under the Advanced SSL/TLS settings section, the Enforce Forward Secrecy field allows you to: Use Global Setting, Enable, or Disable the feature. Enable this option to allow current information to be kept in secrecy, even if the private key is compromised in the future. Note that browsers that do not support Forward Secrecy may not be able to connect to the SRA appliance. The performance of this feature may decline depending on the ciphers that the client browser supports.

Verify Backend SSL Server Certificate for Proxy connections — When this option is enabled, the connection will be dropped if the backend SSL/TLS server certificate is not trusted. The verification depth is 10. Alert level log messages will also be generated when this option is enabled.