Citrix From Chrome

Posted on by



Citrix

  1. Citrix From Chromebook
downloadWhy can't I download this file?

Instructions

1. For an already installed Chrome, Chrome > Settings > Show advanced settings > Privacy > clearing Browsing data: the beginning of time, then exit Chrome and re-run it.
2. Access Netscaler Access Gateway URL in Chrome and login with user credential, You should get below “Detect Receiver” page.
3. Click “Detect Receiver” button and wait, you should see Chrome “External Protocol Request” dialog window pop up.
Note: Verify urlChromebookreceiver://<AG FQDN>/Citrix/…, Verify the client machine can resolve the AG FQDN to correct IP address.
4. Click “Launch Application” button, the expected output is, “Just a moment, we’re detecting if…” and then automatically redirects to Storefront resource enumeration page with resources listed, or Storefront login page (you might need to re-enter user credential and click “Logon” button).
Important Note:
  • If “Just a moment, we’re detecting if…” webpage doesn’t auto redirects to enumeration/login page of storefront, please click “Detect again” button to try again.
  • If “Just a moment, we’re detecting if…” webpage doesn't redirect to storefront web page, it means the configuration for Citrix WebHelper invoked mode failed. In this situation, user can click “Already installed” to continue, Chrome will work in Citrix WebHelper NOT invoked mode.

5. In Storefront resource enumeration page, click an application icon. If “External Protocol Request” dialog window pops up. It indicates Chrome is working at WebHelper.exe invoked mode.
Otherwise, It will work in non-invoked mode. Where it will download ICA file for the resource.
6. Check 'Remember my choice' to avoid repeated External protocol request popup and Click “Launch Application” button, the application should be launched by Receiver successfully even with CST enabled.

Additional Resources

CTX218929: Unable to launch application from Chrome via Netscaler Gateway with client selective trust (CST) enabled
downloadWhy can't I download this file? If the preceding configuration is consistent with the security policy of your organization, an administrator can enable launching applications or desktop using the following steps:

  1. Open a new tab in the Firefox browser.

  2. Type about:config in the address bar.

  3. Double-click network.websocket.allowInsecureFromHTTPS and set the value to true.

Note: This Firefox option might not be supported in Citrix Receiver for HTML5 future versions.

WARNING! This option on Firefox affects the operation of entire Firefox, not just Citrix Receiver for HTML5.

Important Note

As of version 9, Safari browser allows insecure web socket connections. Internet Explorer never allowed non SSL/TLS web socket connections from HTTPS websites. Chrome used to allow it behind a flag, but after the Chrome 44 update, this is no longer supported. Firefox allows it behind a flag (as explained earlier in this article), but it is not recommended. Going forward, only secure (SSL/TLS) web socket connections can be made from Receiver for HTML5.

Problem Cause

When Workspace App for HTML5 is hosted on a https site (default and recommended), non SSL/TLS websocket connections are prohibited by browsers.
In explaining the technical reason behind this it is important to understand the following two principles:
1. As opposed to existing as a separate process, Citrix Workspace App for HTML5 operates within the frame and process space of the browser itself. As such the browser has the ability to enforce certain security parameters.

2. Additionally, when any Workspace App for Windows makes a connection to a VDA for either a published desktop or app, the underlying connection is made to the VDA and not the Storefront server as any kind of intermediate proxy.


This second point is less obvious in the case of Citrix Workspace App for HTML5 because the published desktop or application displays within the browser frame and “appears” to be connected via the Storefront server. Despite this appearance though, the underlying TCP/UDP connection is still between the client and the VDA. If the Storefront base URL is SSL enabled (where it begins with https as is best practice) and the VDA is not SSL enabled (which it is not by default) the browser in this case will prevent the connection due to what it sees as an underlying inconsistency. The inconsistency is that while the URL shown in the browser frame is prefixed with https, the actual underlying connection is not https even though it is not obvious to the user.
There are two solutions for this.
Solution 1 is to enable SSL on the VDA using the following guide:

https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/secure/tls.html
This will ensure that the connection path is SSL enabled between the internal client and the VDA.Download
Solution 2 is to have your connections from the clients first go through a Citrix Gateway. Citrix Gateway will proxy the connections and perform a SSL handshake between the client and the Citrix Gateway. In this scenario there is no inconsistency and connections via HTML5 Receiver will succeed.

Additional Resources

Citrix From Chromebook

You can now use the Application probing feature to proactively monitor the health of applications enabling you to fix issues before the user actually experiences them. For more information refer to Citrix Documentation - Application probing.