Google Chrome Citrix Workspace

  

Text message to imessage

  1. After some extensive googling I came across this post on the Google Help forums Explaining how to white-list specific “browser Protocols” in chrome using a windows registry key. As per example I mentioned above this issue became apparent In my company with users using the citrix receiver or citrix workspace app so the registery key below is.
  2. In this article, Google Chrome on Citrix deep-dive, I will show you how to deploy and configure Google Chrome on Citrix.Using a comprehensive PowerShell script we will automate the unattended installation and some initial configuration for Chrome.

Chrome Version 88.0.4324.146 (Official Build) (64-bit) Ubuntu 20.04 LTS Citrix Workspace 21.1.6.4168 Copy and paste between host and guest does nothing - no indication of errors or issues. There are no settings to adjust. With Google Chrome OS and Citrix Workspace, delivering a secure and robust solution just got easier. Security, speed and flexibility of Chrome OS Wide variety of Chrome devices for every price point and use case Access to over 2M apps in the Google Play Store Manage multiple user devices from a single software system, including Chrome OS, with.

downloadWhy can't I download this file?App

Citrix Receiver for HTML5, Citrix Receiver for Chrome, Citrix Workspace app for Chrome, Citrix workspace app for HTML5

Chrome

Citrix Workspace App On Chromebook

Solution

Recommended solution: Update the certificates.

Alternatively, you can try this workaround:

Citrix Workspace - Google Chrome

  1. Close the Citrix Workspace app for Chrome / Citrix Receiver for Chrome.

  2. Open Chrome browser in your Chromebook.

  3. Visit your site.

  4. It will show some error as below.

Google chrome add citrix workspace

Now, open the Citrix Workspace app for Chrome or Citrix Receiver for Chrome and it might allow you to access your StoreFront/VDA.

Other possible workaround for specific certificate error:

  1. NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM error
    Latest Firefox and Chrome browsers do not support SHA-1 certificate and StoreFront connection fails with error: NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM
    Citrix Receiver for Chrome/HTML5 or Citrix Workspace app for Chrome/HTML5 cannot establish secure connection and session launch will fail

  2. NET::ERR_CERT_COMMON_NAME_INVALID error
    Chrome requires Subject Alternative Name for SHA-2 certificate, without SAN (Subject Alternative Name) in the SHA-2 certificate, the connection will fail with error NET::ERR_CERT_COMMON_NAME_INVALID
    Session launch fails with CERT_COMMON_NAME_INVALID(-200) error dialog
    Workaround for NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM and
    NET::ERR_CERT_COMMON_NAME_INVALID:

    • Mozilla:

      Enable network.websocket.allowInsecureFormHTTPS from about:config

    • Chrome:
      Chrome by default requires SHA2 Certificate with Subject Alternative Names (SAN)
      Add the following registry keys at : SoftwarePoliciesGoogleChrome

    • EnableCommonNameFallbackForLocalAnchors – true
      (Note: Chrome need SAN by default)

    • EnableSha1ForLocalAnchors – true
      (Note: SHA1 is not supported)
      Recommended Solution: Use SHA2 certificates with Subject Alternative Names (SAN).

      Problem Cause:

    • CTX134123 - Receiver for HTML5 - Unable to Launch Apps Using HTTPS URL

    • CTX217352 - How to Collect Logs in Receiver for Chrome and Receiver for HTML5

  3. NET::ERR_CERT_SYMANTEC_LEGACY
    From Chrome OS version 66 onwards the SSL certificate from Symantec is distrusted. You can go through https://security.googleblog.com/2018/03/distrust-of-symantec-pki-immediate.html to know more about it.
    Workaround: Try general workaround mention above.
    Recommended Solution: Update SSL certificates.

Problem Cause

Citrix Workspace App For Chrome

  • CTX134123 - Receiver for HTML5 - Unable to Launch Apps Using HTTPS URL

  • CTX217352 - How to Collect Logs in Receiver for Chrome and Receiver for HTML5