1. Citrix Workspace App Vs Html5
2. Citrix Workspace App For Html5 Free

Recommended solution: Update the certificates.

Reference guide for Citrix Workspace app for HTML5 SDK. Royal mail parcel post box chelmsford. Hides the switchApp button from toolbar, this button appears only for apps session 'preferences'.

Alternatively, you can try this workaround:

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

2. Open Chrome browser in your Chromebook.

3. Visit your site.
   

4. Safeway weekly ad. It will show some error as below.

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

Ive enabled html5 in storefront so users in kiosk machines can access it without downloading receiver. However, since enabling this, chrome and firefox defaults the application launch in HTML5 regardless if the local citrix receiver client is installed. About Citrix Workspace app for Windows. Add accounts or switch servers. Customer Experience Improvement Program (CEIP) Change how desktops look and work.

Other possible workaround for specific certificate error:

Citrix Workspace App Vs Html5

Citrix Workspace App For Html5 Free

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

   • Paradigit laptops & desktops driver download. 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.