![citrix viewer proxytimeout citrix viewer proxytimeout](https://andymorgan.files.wordpress.com/2012/01/example.png)
After you have added the gateway, click for Direct Access and define which controllers should be used against the optimal gateway (And no the Storefront does not need to be able to communicate with the Gateway, since Auth is done completely at Storefront. Specify HDX routing usage only and add the external FQDN of the Gateway. Next we define the Gateway that this store is going to use, this can be done by going into the Store settings –> Optimal HDX Routing Note: We can alter what we want for each website, portal customization can be done under the c:inetpubwwwrootcitrix(nameofwebsite) or using the Storefront GUI. NOTE: I did some changes on the different websites to show how this works from the end-user experience Create the Receiver for web sites needed for the end customers. In my case its just sf. (Setup a wildcard cert on the Storefront server or we can use a SAN or SNI based cert) in my case I have a wildcard cert for the domain Ĭreate a Storefront Store with internal access only, leave everything at default as of now.
CITRIX VIEWER PROXYTIMEOUT VERIFICATION
![citrix viewer proxytimeout citrix viewer proxytimeout](https://theorypc.ca/wp-content/uploads/2019/01/ResourceSelection.png)
We also define that Gateways are being used for HDX routing only, all other auth will happen on Storefront. This feature is not new, but with Storefront 3.1 tech preview this is available in the GUI.
![citrix viewer proxytimeout citrix viewer proxytimeout](https://www.maquinasvirtuales.eu/ipsoapoo/2019/09/citrix-full-screen-desktops-3.png)
Now it is possible to bypass Netscaler authentication, and setup the Gateway vServer just act as a ICA-proxy, so authentication happens at the Storefront but this setup does not work for Receiver.