With Google Chrome OS and Citrix Workspace, delivering a secure and robust solution just got easier. With the in-built security, speed and flexibility of Chrome OS and Chrome Browser, Chrome devices are designed for connecting a mobile workforce to the cloud and delivering fast access to business data. Citrix recommends that you use the web.config file method for configuration purposes only when a store version of Citrix Workspace app for Chrome OS is being used. To change the configuration using the Web.config file: Open the web.config file for the Citrix Receiver for Web site. The Configuration Utility is a UI-based configuration web page that helps administrators customize Citrix Workspace app for Chrome and HTML5 for their enterprise. It is also compatible with Citrix Receiver for Chrome and HTML5. How to use Configuration Utility Steps to Create a Configuration. Users install Citrix Workspace app for Chrome OS from the Chrome Web Store by searching for Citrix Workspace and clicking Add to Chrome. Once installed, Citrix Workspace app for Chrome OS must be configured with connection details for Citrix Gateway and the Citrix Receiver for Web site providing that provides users’ desktops and apps.
- Receiver
Receiver for Chrome Configuration
Created Date: December 19, 2014
Updated Date: December 19, 2014
Description
This is a tool which can be opened in any browser preferably Google Chrome. This tool can create and edit google policy and .cr configuration files easily which can be used to configure Receiver for Chrome.
Prerequisites
Google Chrome/Mozilla Firefox browser.
How to Use Receiver for Chrome Configuration
Today, Citrix Receiver from chrome web store can be configured using .cr files. The .cr file exported from Storefront doesn't have rfweb entry and admin needs to add the entry and distribute the file to various users. Receiver for Chrome can be configured using .cr file using Deploy Receiver for Chrome to your users.
Instead of deploying .cr file to many users, Google policies can be used to configure Receiver for Chrome. This works by using a new feature called App Management which was added in Google Chrome management console for admins to push Chrome app specific policies. To configure Receiver, admin needs to upload a policy text file which contains the settings.
This tool can be used to create/edit the policy file by following the steps mentioned below:
1) Upload an already created .txt google policy file or Enter the appropriate values.
2) Select Google policy as the format to save the information.
3) Click on save button to save the file on the local file system.
Citrix Receiver Chrome Os
The saved policy file created can be directly uploaded in Google Chrome management console to push the policies to Receiver for Chrome.
Note: Google policy required for configuring Receiver for Chrome is currently a tech preview capability from Google. Please contact your Google Sales Representative to get access.
This tool can also be used to create/edit the .cr file that can be distributed to the users to configure Receiver for Chrome in case you cannot use Google Policy.
Additional Resources
1) Sample google policy text file with example URLs generated by this tool:
{
'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://yourcompany.storefrontstoreweb.net'
}
}
}
Citrix Workspace Extension For Chrome
}
}
2) Sample .cr file with the same example URLs generated by this tool:
<Services version='1.0'>
<Service>
<rfWeb>http://yourcompany.storefrontstoreweb.net</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>
Chrome Web Store Citrix Workspace
Disclaimer
Download Citrix Receiver For Chrome
These software applications are provided to you as is with no representations, warranties or conditions of any kind. You may use and distribute it at your own risk. CITRIX DISCLAIMS ALL WARRANTIES WHATSOEVER, EXPRESS, IMPLIED, WRITTEN, ORAL OR STATUTORY, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT. Without limiting the generality of the foregoing, you acknowledge and agree that (a) the software application may exhibit errors, design flaws or other problems, possibly resulting in loss of data or damage to property; (b) it may not be possible to make the software application fully functional; and (c) Citrix may, without notice or liability to you, cease to make available the current version and/or any future versions of the software application. In no event should the code be used to support of ultra-hazardous activities, including but not limited to life support or blasting activities. NEITHER CITRIX NOR ITS AFFILIATES OR AGENTS WILL BE LIABLE, UNDER BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY, FOR ANY DAMAGES WHATSOEVER ARISING FROM USE OF THE SOFTWARE APPLICATION, INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. You agree to indemnify and defend Citrix against any and all claims arising from your use, modification or distribution of the code.
Anyone ever having strange problem to setup SSO from storefront to vad desktop? I'm always using the default internet explorer settings for trusted sites and auto login etc... but in this case:
- Workspace App for Windows installed with SSO option -> SSO works on Win10 client, starting Server 2019 published desktop -> logged in
- Browsing (Tested with IE11, Chrome, MS Edge, same behaviour) to my internal sfweb URL -> SSO works, starting Server 2019 published desktop -> Windows login prompt appears in my published desktop
Citrix Chrome Extension
Whats the difference? Both ways are using the sso settings from the browser, aren't they?