Configure HTML5 Connectivity

The HTML5 tab page is used to configure HTML5 connectivity.

HTML5 connectivity is a functionality built into the RAS Secure Client Gateway. When the connectivity is enabled (default), end users can run published resources using Parallels HTML5 Client that runs inside a web browser . Parallels HTML5 Client works similarly to a platform-specific Parallels Client application with the exception that end users don't have to install any additional software on their computers or devices. All they need is an HTML5-enabled web browser. This section describes how to configure HTML5 connectivity in the Parallels RAS Console. For the information about how to use it, please refer to Using Parallels HTML5 Client .

Note: To use HTML5 connectivity, SSL must be enabled on the Gateway. When enabling HTML5, please verify that SSL is enabled on the SLL/TLS tab page or on your network load balancer.

The HTML5 tab is only available if the gateway mode is set to normal. See Set the Gateway Mode and Forwarding Settings for more info .

To enable HTML5, select the Enable HTML5 Connectivity option. You can also specify a custom port number if necessary.

URL: Indicates the complete URL that end users will need to enter in their web browsers to connect to Parallels RAS. The URL consists of the RAS Secure Client Gateway server FQDN (or computer name) or IP address followed by "RASHTML5Gateway".

Note: You can simplify or even override this URL on the Web Requests tab page of the RAS Secure Client Gateway Properties dialog. For example, you can make it possible for your users to enter just the server FQDN or IP address (without the "RASHTML5Gateway" part) to access the HTML5 login page. If you use HTML5 Client Themes (a Parallels RAS feature), you can specify a URL that will open a particular theme's login page. For more information, please see Specifying a URL for Web Requests and Configure HTML5 Client Themes .

Allow embedding of Web Client into other web pages: If selected, the Parallels HTML5 Client web page can be embedded in other web pages. Please note that this may be a potential security risk due to the practice known as clickjacking.

Launch sessions using: Allows you to specify whether remote applications and desktops will be launched on user computers in a web browser (HTML5 Client) or in a platform-specific Parallels Client. Parallels Client includes a richer set of features compared to HTML5 Client, thus providing end users with a better user experience. Select one of the following:

• Launch apps in browser only (HTML5 only) — Users can run remote applications and desktops using Parallels HTML5 Client only. Use this option if you don't want your users to install a platform-specific Parallels Client for any reason.
• Launch apps in Parallels Client — Users can run remote applications and desktops in Parallels Client only. When a user connects to Parallels RAS using Parallels HTML5 Client, they will be asked to install the platform-specific Parallels Client before they can launch remote applications and desktops. A message will be displayed to the user with a link for downloading the Parallels Client installer. After the user installs Parallels Client, they can still select a remote application or desktop in Parallels HTML5 Client but it will open in Parallels Client instead.
• Launch apps in Parallels Client and fallback to HTML5 — Both Parallels Client and a browser (HTML5) can be used to launch remote applications and desktops. Parallels Client will be the primary method; Parallels HTML5 Client will be used as a backup method if a published resource cannot be launched in Parallels Client for any reason. A user will be informed if a resource couldn't be opened in Parallels Client and will be given a choice to open it in the browser instead.

Allow users to select a launch method — If selected, users will be able to choose whether to open remote applications in a browser or in Parallels Client. You can enable this option only if the Launch session using option (above) is set to Launch apps in Parallels Client and fallback to HTML5 (i.e. both methods are allowed).