Product Documentation

Sample Deployment with SSL Relay and the Web Interface

Oct 09, 2015

This deployment uses the SSL Relay and the Web Interface to encrypt the ICA and HTTP communication between the XenApp server and the Web server, combined with encryption of the HTTP communication between the Web browser and the Web server.

This diagram shows sample deployment D, which uses the SSL Relay and the Web Interface.


The following table lists the components of the deployment and the operating systems required for the servers and client devices.

  Components Operating systems
XenApp farm

XenApp 6.0 for Microsoft Windows Server 2008 R2

SSL Relay enabled

Secure Ticket Authority installed on XenApp server

Windows Server 2008 R2

Web server Web Interface 5.3 for Internet Information Services

Windows Server 2008 R2

Windows Server 2008

Windows Server 2003 with Service Pack 2

.NET Framework 3.5 or 2.0 (IIS 6.0 only)

Visual J#.NET 2.0 Second Edition

User devices

Citrix online plug-in for Windows 12.x

TLS-enabled Web browser

Windows 7

Windows Vista

Windows XP Professional

How the Components Interact

Use HTTPS to secure the connections between users’ Web browsers and the Web Interface. Secure the connection between the Web Interface and the SSL Relay using TLS.

Additionally, use TLS to secure the connections between client devices and the SSL Relay.

The SSL Relay operates as an intermediary in communication between client devices, the Web Interface, and the XML Service on each server. Each client device authenticates the SSL Relay by checking the SSL Relay’s server certificate against a list of trusted certificate authorities. After this authentication, the client device and the SSL Relay negotiate requests in encrypted form. The SSL Relay decrypts the requests and passes them to the XenApp servers. All information sent to the client device from the servers passes through the SSL Relay, which encrypts the data and forwards it to the client device to be decrypted. Message integrity checks verify that each communication has not been tampered with.

This diagram shows a detailed view of sample deployment D.


Security Considerations for This Deployment

FIPS 140 Validation in Sample Deployment D

In this deployment, the SSL Relay uses the Microsoft cryptographic service providers and associated cryptographic algorithms available in the Microsoft Windows CryptoAPI to encrypt and decrypt communication between client devices and servers. For more information about the FIPS 140 validation of the CSPs, see the Microsoft documentation.

For Windows Vista, Windows XP, Windows Server 2008, and Windows Server 2003, TLS/SSL support and the supported ciphersuites can also be controlled using the following Microsoft security option:

System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing

For more information, see the documentation for your operating system.

TLS/SSL Support in Sample Deployment D

You can configure the SSL Relay and the Web Interface to use either the Transport Layer Security 1.0 protocol or the Secure Sockets Layer 3.0 protocol. In sample deployment D, the components are configured for TLS.

When using the SSL Relay Configuration Tool, ensure that TLS is selected on the Connection tab.

Supported Ciphersuites for Sample Deployment D

In this deployment, the SSL Relay and the Web Interface can be configured to use government-approved cryptography, such as the ciphersuite RSA_WITH_3DES_EDE_CBC_SHA, to protect “sensitive but unclassified” data.

When using the SSL Relay Configuration Tool, ensure that only GOV is selected on the Ciphersuite tab.

Alternatively, for TLS connections, you can use AES as defined in FIPS 197. The government ciphersuites are RSA_WITH_AES_128_CBC_SHA for 128-bit keys and RSA_WITH_AES_256_CBC_SHA for 256-bit keys. As defined in Internet RFC 3268 http://www.ietf.org/rfc/rfc3268.txt, these ciphersuites use RSA key exchange and AES encryption. For more information about AES, see http://csrc.nist.gov

Certificates and Certificate Authorities in Sample Deployment D

Citrix products use standard Public Key Infrastructure (PKI) as a framework and trust infrastructure. In sample deployment D, a separate server certificate is configured for each XenApp server on which the SSL Relay is used.

Smart Card Support in Sample Deployment D

In this deployment, you can configure XenApp to provide smart card authentication. To do this, you must configure authentication with Microsoft Active Directory and use the Microsoft Certificate Authority.

Plug-ins Used in Sample Deployment D

In this deployment, users access their applications using the Citrix plug-in. For more information about the security features and capabilities of Citrix plug-ins, see Receiver and Plug-in Security.