Configure

Feature flag management

If an issue occurs with Citrix Workspace app in production, we can disable an affected feature dynamically in Citrix Workspace app even after the feature is shipped. To do so, we use feature flags and a third-party service called LaunchDarkly.

How to configure

You do not need to make any configurations to enable traffic to LaunchDarkly, except when you have a firewall or proxy blocking outbound traffic. In that case, you enable traffic to LaunchDarkly through specific URLs or IP addresses, depending on your policy requirements.

You can enable traffic and communication to LaunchDarkly in the following ways:

Enable traffic to the following URLs

• events.launchdarkly.com
• app.launchdarkly.com
• features.netscalergateway.net

List IP addresses in an allow list

If you must list IP addresses in an allow list, for a list of all current IP address ranges, see LaunchDarkly public IP list. You can use this list to verify your firewall configurations that are updated automatically in keeping with the infrastructure updates. For details about the status of the infrastructure changes, see the LaunchDarkly Status page.

Provision to disable LaunchDarkly service

You can disable LaunchDarkly service on both on-premises and cloud stores.

On the cloud setup, administrators can disable the LaunchDarkly service by setting the enableLaunchDarkly attribute to False in the Global App Configuration service.

For more information, see the Global App Configuration service documentation.

On the on-premises deployment, administrators can disable the LaunchDarkly service using the Google Admin Policy as follows:

1. Sign in to the Google Admin Console.
2. Go to Device management > Chrome Management > User Settings.

3. Add the following strings to the policy.txt file under the engine_settings key.

   "thirdPartyServices": {
   
     "enableLaunchDarkly": false
   
   },
   
   <!--NeedCopy-->
   

4. Click Save.

Note:

• By default, the LaunchDarkly service is enabled if the enableLaunchDarkly attribute isn’t present.

On the on-premises deployment, administrators can disable the LaunchDarkly service using the configuration.js file as follows:

Note:

• Administrator-level credentials are required to edit the configuration.js file; after editing the file, repackage the app for the changes to take effect.

1. Open the configuration.js file.

2. Add the enableLaunchDarkly attribute and set the attribute to false.

   "thirdPartyServices": {
   
       "enableLaunchDarkly": false
   
        },
   <!--NeedCopy-->
   

3. Click Save.

Note:

• By default, the LaunchDarkly service is enabled if the enableLaunchDarkly attribute isn’t present.

Note on Configuration JSON

With the version 2202.1 (22.2.1.8), Citrix Workspace app honors only valid JSON for pushing the configuration. Do the following to validate the JSON file:

1. Verify the JSON data. Use the link https://jsonlint.com/ to verify.

2. Follow the steps mentioned in the Get started page to update:

   • Google Policy
   • web.config
   • default.ica
   • configuration.js

   We recommend using the Configuration utility tool to generate valid JSON settings to customize Citrix Workspace app for ChromeOS using:

   • configuration.js
   • web.config
   • default.ica
   • Google Policy

Note:

You might experience session launch issues when the configuration JSON is invalid.

HTTP proxy setting on Chromebook

In case you have set up the HTTP proxy setting on your Chromebook, it’s possible that your sessions might not start.

To resolve the issue, you can disable the nativeSocket setting on the Google Admin Console and make sure that you’ve enabled the WebSockets connections policy in DDC. For more information, see the WebSocket article.

The following is an example of JSON data:

{
        "settings": {
        "Value": {
              "settings_version": "1.0",
              "engine_settings": {
                         "transport":
                                { "nativeSocket": false
                                  }
                            }
                     }
          }
}
<!--NeedCopy-->

Warning:

Disabling the nativeSocket attribute enables WebSocket connection, which might affect performance in comparison to using a native socket.

Kiosk mode

Citrix Workspace app for ChromeOS kiosk mode helps you to run all apps in the same window. Using this feature, you can run Citrix Workspace apps in kiosk mode, and then launch any Windows app or desktop using the same mode. In addition, kiosk mode allows you to publish remote apps or desktops as a dedicated Chrome package using a persistent URL.

How to configure

You can control this feature by adjusting the kiosk settings in the Chrome admin panel. This setting applies for managed Chrome devices only.

See the Google support site for instructions on enabling the Citrix Workspace app to run in kiosk mode on managed and non-managed Chrome devices.

If you’re deploying a Citrix Workspace app, you must publish using the visibility options set to Public/unlisted to verify interoperability with kiosk mode. Go to the Chrome Web Store Developer Dashboard

The store URL is read-only when kiosk mode is active and can’t be edited using the Account settings screen. However, you can change this setting by either:

• repackaging the app with the .cr file, or
• using the Google Admin Console. Use Google Policy Management to access Google Admin Console.

    <Services version="1.0">
    <Service>
    <rfWeb>http://your_RfWebURL_or_persistenturl</rfWeb>
    <Name>Mystore</Name>
    <Gateways>
    <Gateway>
    <Location>https://yourcompany.gateway.com</Location>
    </Gateway>
    </Gateways>
    <Beacons>
    <Internal>
    <Beacon>http://yourcompany.internalwebsite.net</Beacon>
    </Internal>
    <External>
    <Beacon>http://www.yourcompany.externalwebsite.com</Beacon>
    </External>
    </Beacons>
    </Service>
    </Services>

<!--NeedCopy-->

If you’re using the Google Admin Console, edit the policy.txt file containing the Citrix Workspace configuration. Replace the value of “url” under “rf_web” with a persistent URL.

    {
    "settings": {
    "Value": {
    "settings_version": "1.0",
    "store_settings": {
    "beacons": {
    "external": [
    {
    "url": "http://www.yourcompany.externalwebsite.com"
    }
    ],
    "internal": [
    {
    "url": "http://yourcompany.internalwebsite.net"
    }
    ]
    },
    "gateways": [
    {
    "is_default": true,
    "url": "https://yourcompany.gateway.com"
    }
    ],
    "name": "mystore",
    "rf_web": {
    "url": " http://your_RfWebURL_or_persistenturl "
    }
    }
    }
    }
    }
<!--NeedCopy-->

Global App Configuration service

From this release, as an administrator, you can use the Global App Configuration service to:

• centrally manage and configure app settings and set defaults.
• apply the settings for both managed and unmanaged (BYOD) devices
• apply the settings for both cloud users (domain claimed) and on-premises users (URL claimed).

For more information, see the Global App Configuration service documentation.

Notes:

This feature is available for workspace and HTTPS‑based stores only. For the Global App Configuration service to work, verify if your users can access the URL https://discovery.cem.cloud.us, https://gacs-discovery.cloud.com, and https://gacs-config.cloud.com.