Chapter 8. Client Platforms
To make it easier to test various parameters, the HTML file cgitest.html is included, in the same
location as tlclient.cgi. It also demonstrates how to create icons on web pages, which launches
ThinLinc sessions.
8.7.3. ThinLinc Web Access (HTML5 Client)
The HTML5 client is based on the Open Source project noVNC (http://kanaka.github.io/noVNC/). It
uses HTML5 features such as WebSockets and Canvas. Since this technology is new, only a limited set
of browsers are expected to work. We have tested the latest versions of following browsers:
• Internet Explorer
• Firefox
• Google Chrome
• Safari
Note: At the time of writing, the "Android Browser" does not work since it does not support
WebSockets. For more information, see http://code.google.com/p/android/issues/detail?id=25221.
8.7.3.1. Server Side
The server side components for the HTML5 Client are included in the package thinlinc-webaccess.
It is automatically installed when the ThinLinc software is installed. The default TCP port number for
this HTTP service is 300. It can be changed to some other port such as 443 (see below), assuming this
port is free. The configured port must be allowed in any firewalls. In a cluster setup, the tlwebaccess
service must run on all machines. The same service port should be used, and all machines must be
accessable from the clients. Also, observe the following limitations:
• For best security and user experience, we recommend that you use valid TLS certificates. The
certificates should match the server host names.
• With some browsers such as Safari on iOS, the certificates MUST match the server hostname. This
means that you cannot connect through an IP address. The bundled certificate is created for "localhost"
and cannot be used. You can create a new certificate using our shipped helper script
make-dummy-cert as:
$ sudo /opt/thinlinc/etc/tlwebaccess/make-dummy-cert ‘hostname --fqdn‘
Additionally, a self signed certificate must be manually approved on the iOS device. This can be done
by clicking on the link "Download Server Certificate" in the web interface. This must be done for all
machines in a cluster.
Note: OpenSSL is required to be installed to use the shipped helper script make-dummy-cert.
87
Comentarios a estos manuales