It will automatically start the Configuration Wizard so click OK.
Click OK again.
We’ll go through the Advanced configuration type, so select it and click Advanced.
Select the certificate that you imported earlier and click View.
Confirm that in the Issued to field the fully qualified domain name for the host appears. This must be the same as the server name that the clients will enter in their web browser when accessing the Secure Gateway. Also make sure that it says that there is a private key corresponding to this certificate. Click OK.
Select “Secure Sockets Layer and TLSv1″ and that All is selected for the cipher suite, then click Next.
Accept the default on what to monitor for inbound client connects and click Next.
Click Next.
Click Add to give details on servers running the Secure Ticket Authority (STA). The STA is automatically installed on servers that run the XenApp server role.
Enter the fully qualified domain name the first XenApp server. Use “/Scripts/CtxSTA.dll” for the path, this will point to the library file on the STA even though it is located in the directory “C:\Program Files (x86)\Citrix\system32″. For now we won’t secure traffic between the STA and Secure Gateway so make sure that is not checked. In the TCP port field make sure this is the same as the Citrix XML Service port you’ve configured on your XenApp servers. Click OK.
It is desirable to specify a second and third server running the STA. I only have one XenApp server configured, so I’ll click Next.
Click Next unless you want to change connection timeout and limits.
Click Next.
I’ll keep Indirect selected for Access options, I want my external clients to enter the Secure Gateway URL in their web browser. Keep 80 in the TCP port details for the port that the Web Interface listens to for http requests.
Click Next.
Click Finish to start the Secure Gateway.
No comments:
Post a Comment