Wednesday, May 21, 2014

Working with Horizon Workspace Virtual Users and zmprov

One nifty feature of Horizon Workspace is the ability to share files and folders with external users. An "external user" could mean one of two things:

  1. A directory server user not synced to Horizon Workspace

  2. Someone outside of the enterprise


An invited user is then created as a virtual user in the Workspace instance. You can find more information about virtual users in the Horizon Workspace Administrator's Guide under User and Group Types: http://hrzn.ws/1nqI0ZS


When a virtual user is created, they are assigned to a hidden Class of Service (COS) called defaultExternal. This class of service comes with its own parameters, notably, all virtual users are defaulted to a file upload size of 2GB. You may notice the following error when a virtual user tries to upload a file larger than 2GB:


exceeds single file maximum upload size 2147483648 bytes


Additionally, the virtual user will share the quota of the internal user that shared the file with them. So if the inviter has an unlimited quota, files the invitee uploads won't have a negative impact. Conversely, if the inviter has a 10GB limit, any file the invitee uploads will go toward that internal user's 10GB quota.


So how can we increase the virtual user's file upload size limit?

Though the defaultExternal COS is hidden in the Administration Console, you can still configure its attributes via the data-va command line.
 

To change the upload file size limit for virtual users:


  1. Login to the data-va as root

  2. Change to the zimbra user:

    sudo su - zimbra

  3. Switch to the virtual user tenant and modify the upload attribute to the desired file size limit, in bytes:
    $ zmprov
    prov> st __virtual__
    prov> mc defaultExternal hzndataFileUploadMaxSize filesize-in-bytes
    prov> mc defaultExternal hzndataFileUploadMaxSizePerFile filesize-in-bytes
    prov> quit











    Increasing virtual user file upload limit to 3GB


  4. Restart the service

    zmcontrol restart



Note: to clear the Tenant specifier back to default, use the unsetTenant command:

$ zmprov

prov> ut

To view all COS, you can use 'gac.' Notice my example below doesn't show defaultExternal because I do not have any virtual users:

Additionally you can run "zmprov gac -v" which will show all the configured attributes for each COS. The process outlined above can be used to edit any COS manually. Keep in mind a COS you've created in the Administrator Console GUI will be in the default tentant, not the __virtual__ tenant.

Happy modding!
Share:

Thursday, May 15, 2014

Logging into Horizon Workspace fails: We were unable to authenticate you

This error can be pesky as it is a bit misleading. The full error will read something similar to
We were unable to authenticate you. Please check your credentials and try again.

Furthermore, you may notice whenever you load the Workspace login page a notice at the top that reads
Identity provider's url scheme mismatches with that of the request. This could happen when the request is received on https and the Identity provider's is running on http.

This behavior is usually caused by our IdP trying to use port 443 but SSL authentication is disabled. To resolve this issue:

  1. Login to the connector-va web page

  2. Click on Identity Providers

  3. Verify the IdP hostname is correct and using port 443

  4. Check the box to Use SSL for end-user authentication

  5. Click Save




 

 

Give that user's login another go and you should be on your way.
Share:

Follow by Email