Gateway

Deploy Citrix Gateway with the Web Interface

January 8, 2024

Contributed by:

When you deploy Citrix Gateway to provide secure remote access to Citrix Virtual Apps and Desktops, Citrix Gateway is compatible with the Web Interface and the Secure Ticket Authority (STA) to provide access to published applications and desktops hosted in a server farm.

Deploying Citrix Gateway in the DMZ is the most common configuration when Citrix Gateway operates with a server farm. In this configuration, Citrix Gateway provides a secure single point-of-access for the web browsers and Citrix Workspace app that access the published resources through the Web Interface. This section covers the basic aspects of about this deployment option.

The configuration of your organization’s network determines where you deploy Citrix Gateway when it operates with a server farm. You have the following two options:

If your organization protects the internal network with a single DMZ, deploy Citrix Gateway in the DMZ.
If your organization protects the internal network with two DMZs, deploy one Citrix Gateway in each of the two network segments in a double-hop DMZ configuration. For more information, see Deploying Citrix Gateway in a Double-Hop DMZ. Note: You can also configure a double-hop DMZ with the second Citrix Gateway appliance in the secure network.

When you deploy Citrix Gateway in the DMZ to provide remote access to a server farm, you can implement one of the following three deployment options:

Deploy the Web Interface behind Citrix Gateway in the DMZ. In this configuration, as shown in the following figure, both Citrix Gateway and the Web Interface are deployed in the DMZ. The initial user connection goes to Citrix Gateway and is then redirected to the Web Interface. Figure 1. Web Interface Behind Citrix Gateway in the DMZ
Deploy Citrix Gateway parallel to the Web Interface in the DMZ. In this configuration, both Citrix Gateway and the Web Interface are deployed in the DMZ, but the initial user connection goes to the Web Interface instead of Citrix Gateway.
Deploy Citrix Gateway in the DMZ and deploy the Web Interface in the internal network. In this configuration, Citrix Gateway authenticates user requests before relaying the request to the Web Interface in the secure network. The Web Interface does not perform authentication, but interacts with the STA and generates an ICA file to ensure that ICA traffic is routed through Citrix Gateway to the server farm.

The location in which you deploy the Web Interface depends on various factors, including:

Authentication. When users log on, either Citrix Gateway or the Web Interface can authenticate user credentials. Where you place the Web Interface in your network is a factor that determines, in part, where users authenticate.
User software. Users can connect to the Web Interface with either the Citrix Gateway plug-in or Citrix Workspace app. You can limit the resources users can access by using Citrix Workspace app only, or give users greater network access with the Citrix Gateway plug-in. How users connect, and the resources to which you allow users to connect can help determine where you deploy the Web Interface in your network.

Deploy the Web Interface in a secure network

In this deployment, the Web Interface resides in the secure, internal network. Citrix Gateway is in the DMZ. Citrix Gateway authenticates user requests before sending the requests to the Web Interface.

When you deploy the Web Interface in the secure network, you must configure authentication on Citrix Gateway.

If you deploy the Web Interface with Citrix Virtual Apps and Desktops, deploying the Web Interface in the secure network is the default deployment scenario. When the Desktop Delivery Controller is installed, a custom version of the Web Interface is also installed.

Important: When the Web Interface is in the secure network, you must enable authentication on Citrix Gateway. Users connect to Citrix Gateway, type their credentials, and then connect to the Web Interface. When you disable authentication, unauthenticated HTTP requests are sent directly to the server running the Web Interface. Disabling authentication on Citrix Gateway is recommended only when the Web Interface is in the DMZ and users connect directly to the Web Interface.

Figure 1. Web Interface Located Inside the Secure Network

Deployment illustration

Deploy the Web Interface parallel to Citrix Gateway in a DMZ

In this deployment, the Web Interface and Citrix Gateway both reside in the DMZ. Users connect directly to the Web Interface by using a web browser or Citrix Workspace app. User connections are first sent to the Web Interface for authentication. After authentication, the connections are routed through Citrix Gateway. After users log on successfully to the Web Interface, they can access published applications or desktops in the server farm. When users start an application or desktop, the Web Interface sends an ICA file containing instructions for routing ICA traffic through Citrix Gateway as if it were a server running the Secure Gateway. The ICA file delivered by the Web Interface includes a session ticket produced by the Secure Ticket Authority (STA).

When Citrix Workspace app connects to Citrix Gateway, the ticket is presented. Citrix Gateway contacts the STA to validate the session ticket. If the ticket is still valid, the user’s ICA traffic is relayed to the server in the server farm. The following figure shows this deployment.

Figure 1. The Web Interface installed parallel to Citrix Gateway

Web Interface Running Parallel to Citrix Gateway

When the Web Interface runs parallel to Citrix Gateway in the DMZ, you do not need to configure authentication on Citrix Gateway. The Web Interface authenticates users.

Deploy the Web Interface behind Citrix Gateway in a DMZ

In this configuration, both Citrix Gateway and the Web Interface are deployed in the DMZ. When users log on with Citrix Workspace app, the initial user connection goes to Citrix Gateway and is then redirected to the Web Interface. To route all HTTPS and ICA traffic through a single external port and require the use of a single SSL certificate, Citrix Gateway acts as a reverse web proxy for the Web Interface.

Figure 1. Web Interface Located Behind Citrix Gateway

Deployment illustration

When the Web Interface is deployed behind Citrix Gateway in the DMZ, you can configure authentication on the appliance but it is not required. You can have either Citrix Gateway or the Web Interface authenticates users because both reside in the DMZ.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Deploy Citrix Gateway with the Web Interface

January 8, 2024

Contributed by:

January 8, 2024

Contributed by:

Deploy Citrix Gateway with the Web Interface

Deploy the Web Interface in a secure network

Deploy the Web Interface parallel to Citrix Gateway in a DMZ

Deploy the Web Interface behind Citrix Gateway in a DMZ

In this article