-
Install and configure the Citrix Gateway appliance
-
Deploy Citrix Gateway in a double-hop DMZ
-
Maintain and monitor Citrix Gateway systems
-
VPN configuration on a Citrix Gateway appliance
-
Integrate the Citrix Gateway plug-in with Citrix Workspace app
-
Configure DTLS VPN virtual server using SSL VPN virtual server
-
Integrate Citrix Gateway with Citrix products
-
Integrate Citrix Gateway with Citrix Virtual Apps and Desktops
-
Configure settings for your Citrix Endpoint Management Environment
-
Configure load balancing servers for Citrix Endpoint Management
-
Configure load balancing servers for Microsoft Exchange with Email Security Filtering
-
Configure Citrix Endpoint Management NetScaler Connector (XNC) ActiveSync Filtering
-
Allow Access from mobile devices with Citrix Mobile Productivity Apps
-
Configure domain and security token authentication for Citrix Endpoint Management
-
Configure client certificate or client certificate and domain authentication
-
-
Citrix Gateway Enabled PCoIP Proxy Support for VMware Horizon View
-
Proxy Auto Configuration for Outbound Proxy support for Citrix Gateway
-
Access Citrix Virtual Apps and Desktops resources with the Web Interface
-
Configuring Communication with the Web Interface
-
Configuring Policies for Published Applications and Desktops
-
Configuring the Secure Ticket Authority on Citrix Gateway
-
-
Configuring Additional Web Interface Settings on Citrix Gateway
-
Configuring Access to Applications and Virtual Desktops in the Web Interface
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Configuring the Secure Ticket Authority on Citrix Gateway
The Secure Ticket Authority (STA) is responsible for issuing session tickets in response to connection requests for published applications on Citrix Virtual Apps and published desktops on Citrix Virtual Desktops. These session tickets form the basis of authentication and authorization for access to published resources.
You can bind the STA globally or to virtual servers. You can also add multiple servers running the STA when you configure a virtual server.
If you are securing communications between the Citrix Gateway and the STA, make sure that a server certificate is installed on the server running the STA.
In a typical Citrix Gateway GSLB deployment, all gateway virtual servers (in each site) must be configured with the same back-end STA servers to avoid reconnection issues.
Note:
If STA servers are configured to use HTTP protocol (for example, http://staFQDN.com) and the delivery controller (DDC) uses HTTPS, the connection fails. This failure occurs because the DNS resolution or any probe attempting to communicate with the STA server using the incorrect protocol does not succeed. It is essential to ensure that the STA server URLs are updated to use HTTPS to match the DDC configuration.
For more information on when it is appropriate to use HTTP vs HTTPS, when to use FQDN over IP address for different STA use cases, and how to protect STA traffic with SSL, see NetScaler Gateway Secure Ticket Authority.
For cloud connectors to support HTTPS STA configuration, set
XmlServicesEnableSsl
to1
on cloud connector and restart the Citrix Remote Broker Provider service and the Citrix High Availability service. For more information, see Secure Ticket Authority (STA) Showing Offline and 503 Error in a Browser.
To bind the STA globally
- Navigate to Citrix Gateway > Global Settings.
- In the details pane, under Servers, click Bind/Unbind STA Servers to be used by the Secure Ticket Authority.
- In the Bind/Unbind STA Servers dialog box, click Add.
- In the Configure STA Server dialog box, enter the URL of the STA server, click Create, and then click OK.
- In the STA Server dialog box, in URL, type the IP address or fully qualified domain name (FQDN) of the server running the STA and then click Create.
Note: You can add more than one server running the STA to the list. The STAs that are listed in the Web Interface must match the STAs that are configured on Citrix Gateway. If you are configuring multiple STAs, do not use load balancing between Citrix Gateway and the servers running the STA.
To bind a STA to the virtual server
- Navigate to Citrix Gateway > Virtual Servers.
- In the details pane, select a virtual server and then click Edit.
- On the Published Applications tab under Secure Ticket Authority, click Add.
- In the Configure STA Server dialog box, enter the URL of the STA server and then click Create.
- Repeat Step 4 to add additional STA servers and then click OK.
References
-
For details about STA, see the article NetScaler Gateway Secure Ticket Authority.
-
For details on configuring your Citrix Gateway to use a Cloud Connector as the Secure Ticket Authority (STA) server, see How do I configure Citrix Gateway to use a Cloud Connector as a STA.
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.