Skip to content
This repository has been archived by the owner on Dec 20, 2023. It is now read-only.

Remove zimbraProxyAllowedDomains

Pre-release
Pre-release
Compare
Choose a tag to compare
@barrydegraaff barrydegraaff released this 18 Oct 13:47
· 549 commits to soapServiceBarry since this release
0.5.6
2e4291b

As of version 0.5.6 your clients CAN CONNECT TO ALL DAV SERVERS BY DEFAULT,
you can restrict the allowed DAV servers to connect to in:

/opt/zimbra/lib/ext/ownCloud/config.properties
allowdomains=allowme.example.com;allowmealso.example.com

  • No service restart is needed after changing this file.

    If you installed WebDAV Client before, you should remove your DAV servers
    from zimbraProxyAllowedDomains:
    zmprov gc default zimbraProxyAllowedDomains
    zmprov mc default -zimbraProxyAllowedDomains allowme.example.com

Make sure to download the latest installer!
wget https://raw.githubusercontent.com/Zimbra-Community/owncloud-zimlet/soapServiceBarry/webdav-client-installer.sh -O /tmp/webdav-client-installer.sh
chmod +rx /tmp/webdav-client-installer.sh
/tmp/webdav-client-installer.sh

This change has been made to separate the WebDAV Client configuration from the Zimbra Proxy Servlet.

In older versions one could use proxy servlet to access DAV files (if you have enough credentials):
https://zimbra.example.com/service/proxy?target=https://myzimbra.com/owncloud/remote.php/webdav/folder/file.zip

Now you can opt not to allow this servlet, and this can increase security
in scenarios where your DAV server is only accessible in a LAN or vlan.

Assets 2