Secure user sessions using TLS
Starting with Version 7.16, the Linux VDA supports TLS encryption for secure user sessions. TLS encryption is disabled by default.
Enable TLS encryption
To enable TLS encryption for secure user sessions, install certificates and enable TLS encryption on both the Linux VDA and the Delivery Controller (the Controller).
Obtain server certificates in PEM format and root certificates in CRT format. A server certificate contains the following sections:
- Unencrypted private key
- Intermediate certificates (optional)
An example of a server certificate:
On the Linux VDA, use the
enable_vdassl.sh script in the /opt/Citrix/VDA/sbin directory to enable (or disable) TLS encryption. For information about the options available in the script, run the
/opt/Citrix/VDA/sbin/enable_vdassl.sh -help command.
Tip: A server certificate must be installed on each Linux VDA server and root certificates must be installed on each Linux VDA server and client.
You can enable TLS encryption only for entire delivery groups. You cannot enable TLS encryption for specific applications.
In a PowerShell window on the Controller, run the following commands in sequence to enable TLS encryption for the target delivery group.
Get-BrokerAccessPolicyRule –DesktopGroupName 'GROUPNAME' | Set-BrokerAccessPolicyRule –HdxSslEnabled $true
To ensure that only VDA FQDNs are contained in an ICA session file, you can also run the
Set-BrokerSite –DnsResolutionEnabled $truecommand. The command enables DNS resolution. If you disable DNS resolution, an ICA session file discloses VDA IP addresses and provides FQDNs only for the TLS-related items such as
To disable TLS encryption on the Controller, run the following commands in sequence:
Get-BrokerAccessPolicyRule –DesktopGroupName 'GROUPNAME' | Set-BrokerAccessPolicyRule –HdxSslEnabled $false
Set-BrokerSite –DnsResolutionEnabled $false
The following “Can’t assign requested address” error might occur in Citrix Workspace app for Windows when you try to access a published desktop session:
As a workaround, add an entry to the hosts file, which is similar to:
<IP address of the Linux VDA> <FQDN of the Linux VDA>
On Windows machines, the hosts file typically locates at