Locate the following section in the file.Ĭhange the setting for the menubar attribute to false. Use a text editor to open the configuration.js file in the Citrix Workspace app for ChromeApp root directory. Note: We recommend that you back up the configuration.js file before making any changes to it. If you want to disable the in-session toolbar perform the following steps. Rename the modified configuration file to default.cr and copy it to the Citrix Workspace app for Chrome OS root directory.Ĭonfiguration files with different names or in other locations are not included when Citrix Workspace app for Chrome OS is repackaged.īy default, the in-session toolbar is enabled. Users can start working with Citrix Workspace app for Chrome OS as soon as they have installed it without the need to perform any additional configuration steps.ĭownload the unpackaged version of Citrix Workspace app for Chrome OS to a suitable location.ĭownload the sample configuration file and customize it as appropriate for your environment. cr file to preconfigure Citrix Workspace app for Chrome OS with the appropriate connection details for your environment. To simplify the deployment process for users, you can repackage Citrix Workspace app for Chrome OS with a new.
crx file to users through other means, such as through email.
For more information on Chrome OS configuration, see Knowledge Center article CTX141844. You can use Google App management console to configure Citrix Workspace using Google policy.
Recommended Solution: Update SSL certificates.There are a number of options for deploying Citrix Workspace app for Chrome OS. Workaround: Try general workaround mention above. You can go through to know more about it.
Recommended Solution: Use SHA2 certificates with Subject Alternative Names (SAN).ĬTX134123 - Receiver for HTML5 - Unable to Launch Apps Using HTTPS URLĬTX217352 - How to Collect Logs in Receiver for Chrome and Receiver for HTML5įrom Chrome OS version 66 onwards the SSL certificate from Symantec is distrusted. Workaround for NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM andĮnable from about:configĬhrome by default requires SHA2 Certificate with Subject Alternative Names (SAN)Īdd the following registry keys at : Software\Policies\Google\Chrome\ĮnableCommonNameFallbackForLocalAnchors – true Session launch fails with CERT_COMMON_NAME_INVALID(-200) error dialog Latest Firefox and Chrome browsers do not support SHA-1 certificate and StoreFront connection fails with error: NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHMĬitrix Receiver for Chrome/HTML5 or Citrix Workspace app for Chrome/HTML5 cannot establish secure connection and session launch will failĬhrome 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
NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM error Other possible workaround for specific certificate error: Now, open the Citrix Workspace app for Chrome or Citrix Receiver for Chrome and it might allow you to access your StoreFront/VDA. Alternatively, you can try this workaround:Ĭlose the Citrix Workspace app for Chrome / Citrix Receiver for Chrome. Recommended solution: Update the certificates.