-
-
Configuring the VPN User Experience
-
How User Connections Work with the NetScaler Gateway Plug-in
-
Integrating the NetScaler Gateway Plug-in with Citrix Receiver
-
-
-
Installing and Configuring Netscaler Gateway in a Double-Hop DMZ
-
Configuring Settings on the Virtual Servers on the NetScaler Gateway Proxy
-
Configuring the Appliance to Communicate with the Appliance Proxy
-
Configuring NetScaler Gateway to Handle the STA and ICA Traffic
-
Managing SSL Certificates in a Double-Hop DMZ Deployment
-
-
Maintaining and Monitoring the System
-
Deploying with XenMobile App Edition, XenApp, and XenDesktop
-
Accessing XenApp and XenDesktop Resources with the Web Interface
-
Configuring Additional Web Interface Settings on NetScaler Gateway
-
Configuring Access to Applications and Virtual Desktops in the Web Interface
-
Configuring Settings for Your XenMobile Environment
-
Configuring Load Balancing Servers for Microsoft Exchange with Email Security Filtering
-
Configuring XenMobile NetScaler Connector (XNC) ActiveSync Filtering
-
Configuring Domain and Security Token Authentication for XenMobile
-
Configuring Client Certificate or Client Certificate and Domain Authentication
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!
Managing SSL Certificates in a Double-Hop DMZ Deployment
You must install the SSL certificates necessary to encrypt the connections among components in a double-hop DMZ deployment.
In a double-hop DMZ deployment, several different types of connections occur among the various components involved in the deployment. There is no end-to-end SSL encryption of these connections. However, each connection can be encrypted individually.
Encrypting a connection requires you to install the appropriate SSL certificate (either a trusted root or a server certificate) on the components involved in the connection.
The following table shows the connections that occur through the first firewall and the SSL certificates required to encrypt each of these connections. Encrypting the connections through the first firewall is mandatory to secure traffic sent over the Internet.
Connections through the first firewall | Certificates required for encryption |
---|---|
The web browser from the Internet connects to NetScaler Gateway in the first DMZ. | NetScaler Gateway in the first DMZ must have an SSL server certificate installed. The web browser must have a root certificate installed that is signed by the same Certificate Authority (CA) as the server certificate on NetScaler Gateway. |
Citrix Receiver from the Internet connects to NetScaler Gateway in the first DMZ. | The certificate management for this connection is the same as the web browser to NetScaler Gateway connection. If you installed the certificates to encrypt the web browser connection, this connection is also encrypted using those certificates. |
The following table shows the connections that occur through the second firewall and the SSL certificates required to encrypt each of these connections. Encrypting these connections enhances security but is not mandatory.
Connections through the second firewall | Certificates required for encryption |
---|---|
NetScaler Gateway in the first DMZ connects to the Web Interface in the second DMZ. | StoreFront or the Web Interface must have an SSL server certificate installed. NetScaler Gateway in the first DMZ must have a root certificate installed that is signed by the same CA as the server certificate on the Web Interface. |
NetScaler Gateway in the first DMZ connects to NetScaler Gateway in the second DMZ. | NetScaler Gateway in the second DMZ must have an SSL server certificate installed. NetScaler Gateway in the first DMZ must have a root certificate installed that is signed by the same CA as the server certificate on NetScaler Gateway in the second DMZ. |
The following table below shows the connections that occur through the third firewall and the SSL certificates required to encrypt each of these connections. Encrypting these connections enhances security but is not mandatory.
Connections through the third firewall | Certificates required for encryption |
---|---|
StoreFront or the Web Interface in the second DMZ connects to the XML Service hosted on a server in the internal network. | If the XML Service runs on Microsoft Internet Information Services (IIS) server on the XenApp server, an SSL server certificate must be installed on the IIS server. If the XML Service is a standard Windows service (does not reside in IIS), an SSL server certificate must be installed within the SSL Relay on the server. StoreFront or the Web Interface must have a root certificate installed that is signed by the same CA as the server certificate installed on either the Microsoft IIS server or the SSL Relay. |
StoreFront or the Web Interface in the second DMZ connects to the STA hosted on a server in the internal network. | The certificate management for this connection is the same as the Web Interface to XML Service connection. You can use the same certificates to encrypt this connection. (The server certificate must reside on either the Microsoft IIS server or the SSL Relay. A corresponding root certificate must be installed on the Web Interface.) |
NetScaler Gateway in the second DMZ connects to the STA hosted on a server in the internal network. | The SSL server certificate management for the STA in this connection is the same as described for the two previous connections discussed in this table. (The server certificate must reside on either the Microsoft IIS server or the SSL Relay.) NetScaler Gateway in the second DMZ must have a root certificate installed that is signed by the same CA as the server certificate used by the STA and XML service. |
NetScaler Gateway in the second DMZ makes an ICA connection to a published application on a server in the internal network. | An SSL server certificate must be installed within the SSL Relay on the server hosting the published application. NetScaler Gateway proxy in the second DMZ must have a root certificate installed that is signed by the same CA as the server certificate installed within the SSL Relay. |
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix 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 Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.