Collaboration platform fully supports the WebDAV protocol, and you can connect and synchronize with your Collaboration platform files over WebDAV. In this chapter you will learn how to connect Linux, macOS, Windows, and mobile devices to your Collaboration platform server via WebDAV. Before we get into configuring WebDAV, let’s take a quick look at the recommended way of connecting client devices to your Collaboration platform servers.
In the following examples, you should replace example.com/collaboration-platform with the URL of your Collaboration platform server (omit the directory part if the installation is in the root of your domain), and “USERNAME” with the username of the connecting user.
See the WebDAV URL (bottom left in settings) on your Collaboration platform.
In the following examples, you must use an app-password for login, which you can generate in your security settings.
The recommended way to synchronize a desktop PC with a Collaboration platform server is by using Collaboration platform/ownCloud sync clients. You can configure the client to save files in any local directory and you can choose which directories on the Collaboration platform server to sync with. The client displays the current connection status and logs all activity, so you always know which remote files have been downloaded to your PC and you can verify that files created and updated on your local PC are properly synchronized with the server.
The recommended way to synchronize Collaboration platform server with Android and Apple iOS devices is by using the mobile apps.
To connect your mobile app to a Collaboration platform server use the base URL and folder only:
In addition to the mobile apps provided by Collaboration platform or ownCloud, you can use other apps to connect to Collaboration platform from your mobile device using WebDAV. WebDAV Navigator is a good (proprietary) app for Android devices and iPhones. The URL to use on these is:
When you configure your Collaboration platform account in the GNOME Control Center, your files will automatically be mounted by Nautilus as a WebDAV share, unless you deselect file access.
You can also mount your Collaboration platform files manually. Use the davs:// protocol to connect the Nautilus file manager to your Collaboration platform share:
If your server connection is not HTTPS-secured, use dav:// instead of davs://:
The same method works for other file managers that use GVfs, such as MATE’s Caja and Cinnamon’s Nepomuk.
To access your Collaboration platform files using the Dolphin file manager in KDE, use the webdav:// protocol:
You can create a permanent link to your Collaboration platform server:
1. Open Dolphin and click “Network” in the left hand “Places” column.
2. Click on the icon labeled Add a Network Folder. The resulting dialog should appear with WebDAV already selected.
3. If WebDAV is not selected, select it.
4. Click Next.
5. Enter the following settings:
6. (Optional) Check the “Create icon” checkbox for a bookmark to appear in the Places column.
7. (Optional) Provide any special settings or an SSL certificate in the “Port & Encrypted” checkbox.
You can create WebDAV mounts from the Linux command line. This is useful if you prefer to access Collaboration platform the same way as any other remote filesystem mount. The following example shows how to create a personal mount and have it mounted automatically every time you log in to your Linux computer.
1. Install the davfs2 WebDAV filesystem driver, which allows you to mount WebDAV shares just like any other remote filesystem. Use this command to install it on Debian/Ubuntu:
apt-get install davfs2
2. Use this command to install it on CentOS, Fedora, and openSUSE:
yum install davfs2
3. Add yourself to the davfs2 group:
usermod -aG davfs2
4. Then create a Collaboration platform directory in your home directory for the mountpoint, and .davfs2/ for your personal configuration file:
5. Copy /etc/davfs2/secrets to ~/.davfs2:
cp /etc/davfs2/secrets ~/.davfs2/secrets
6. Set yourself as the owner and make the permissions read-write owner only:
chown : ~/.davfs2/secrets
chmod 600 ~/.davfs2/secrets
7. Add your Collaboration platform login credentials to the end of the secrets file, using your Collaboration platform server URL and your Collaboration platform username and password:
$PathToMountPoint $USERNAME $PASSWORD
/home/user/collaboration-platform john 1234
8. Add the mount information to /etc/fstab:
davfs user,rw,auto 0 0
9. Then test that it mounts and authenticates by running the following command. If you set it up correctly you won’t need root permissions:
10. You should also be able to unmount it:
Now every time you login to your Linux system your Collaboration platform share should automatically mount via WebDAV in your ~/Collaboration platform directory. If you prefer to mount it manually, change auto to noauto in /etc/fstab.
Resource temporarily unavailable
If you experience trouble when you create a file in the directory, edit /etc/davfs2/davfs2.conf and add:
If you use a self-signed certificate, you will get a warning. To change this, you need to configure davfs2 to recognize your certificate. Copy mycertificate.pem to /etc/davfs2/certs/. Then edit /etc/davfs2/davfs2.conf and uncomment the line servercert. Now add the path of your certificate as in this example:
The macOS Finder suffers from a series of implementation problems and should only be used if the Collaboration platform server runs on Apache and mod_php, or Nginx 1.3.8+. Alternative macOS-compatible clients capable of accessing WebDAV shares include open source apps like Cyberduck (see instructions here) and Filezilla. Commercial clients include Mountain Duck, Forklift, Transmit, and Commander One.
To access files through the macOS Finder:
1. From the Finder’s top menu bar, choose Go > Connect to Server…:
If you use the native Windows implementation of WebDAV, you can map Collaboration platform to a new drive using Windows Explorer. Mapping to a drive enables you to browse files stored on a Collaboration platform server the way you would files stored in a mapped network drive.
Using this feature requires network connectivity. If you want to store your files offline, use the Desktop Client to sync all files on your Collaboration platform to one or more directories of your local hard drive.
Windows 10 now defaults to allow Basic Authentication if HTTPS is enabled prior to mapping your drive. On older versions of Windows, you must permit the use of Basic Authentication in the Windows Registry: launch regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters. Create or edit the DWORD value BasicAuthLevel (Windows Vista, 7 and 8) or UseBasicAuth (Windows XP and Windows Server 2003) and set its value data to 1 for SSL connections. Value 0 means that Basic Authentication is disabled, a value of 2 allows both SSL and non-SSL connections (not recommended). Then exit Registry Editor, and restart the computer.
The following example shows how to map a drive using the command line. To map the drive:
1. Open a command prompt in Windows.
2. Enter the following line in the command prompt to map to the computer Z drive:
net use Z: https:///remote.php/dav/files/USERNAME/ /user:youruser
where is the URL to your Collaboration platform server.
For example: net use Z: https://example.com/Collaboration-platform
/remote.php/dav/files/USERNAME/ /user:youruser yourpassword
The computer maps the files of your Collaboration platform account to the drive letter Z.
Though not recommended, you can also mount the Collaboration platform server using HTTP, leaving the connection unencrypted. If you plan to use HTTP connections on devices while in a public place, we strongly recommend using a VPN tunnel to provide the necessary security.
An alternative command syntax is:
To map a drive using the Microsoft Windows Explorer:
1. Open Windows Explorer on your MS Windows computer.
2. Right-click on Computer entry and select Map network drive… from the drop-down menu.
3. Choose a local network drive to which you want to map Collaboration platform.
4. Specify the address to your Collaboration platform
instance, followed by /remote.php/dav/files/USERNAME/.
For SSL protected servers, check Reconnect at sign-in to ensure that the mapping is persistent upon subsequent reboots. If you want to connect to the Collaboration platform server as a different user, check Connect using different credentials.
Cyberduck is an open source FTP and SFTP, WebDAV, OpenStack Swift, and Amazon S3 browser designed for file transfers on macOS and Windows.
This example uses Cyberduck version 4.2.1.
To use Cyberduck:
1. Specify a server without any leading protocol information. For example:
2. Specify the appropriate port. The port you choose depends on whether or not your Collaboration platform
server supports SSL. Cyberduck requires that you select a different connection type if you plan to use SSL. For example:
80 (for WebDAV)
443 (for WebDAV (HTTPS/SSL))
3. Use the ‘More Options’ drop-down menu to add the rest of your WebDAV URL into the ‘Path’ field. For example:
Now Cyberduck enables file access to the Collaboration platform server.
Collaboration platform provides the possibility to access public shares anonymously over WebDAV.
To access the public share, open:
in a WebDAV client, use the share token as username and the (optional) share password as password. For example, with a share link https://example.com/s/kFy9Lek5sm928xP, kFy9Lek5sm928xP will be the username.
Settings → Administration → Sharing → Allow users on this server to send shares to other servers. This option also allows WebDAV access to public shares needs to be enabled in order to make this feature work, except if cURL is being used (see below).
Windows does not connect using HTTPS.
The Windows WebDAV Client might not support Server Name Indication (SNI) on encrypted connections. If you encounter an error mounting an SSL-encrypted Collaboration platform instance, contact your provider about assigning a dedicated IP address for your SSL-based server.
The Windows WebDAV Client might not support TLSv1.1 and TLSv1.2 connections. If you have restricted your server config to only provide TLSv1.1 and above the connection to your server might fail. Please refer to the WinHTTP documentation for further information.
You receive the following error message: Error 0x800700DF: The file size exceeds the limit allowed and cannot be saved.
Windows limits the maximum size a file transferred from or to a WebDAV share may have. You can increase the value FileSizeLimitInBytes in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters by clicking on Modify.
To increase the limit to the maximum value of 4GB, select Decimal, enter a value of 4294967295, and reboot Windows or restart the WebClient service.
Accessing your files from Microsoft Office via WebDAV fails.
Known problems and their solutions are documented in the KB2123563 article.
Cannot map Collaboration platform as a WebDAV drive in Windows using self-signed certificate.
1. Go to the your Collaboration platform instance via your favorite Web browser.
2. Click through until you get to the certificate error in the browser status line.
3. View the cert, then from the Details tab, select Copy to File.
4. Save to the desktop with an arbitrary name, for example mycollaboration platform.pem.
5. Start, Run, MMC.
6. File, Add/Remove Snap-In.
7. Select Certificates, Click Add, My User Account, then Finish, then OK.
8. Dig down to Trust Root Certification Authorities, Certificates.
9. Right-Click Certificate, Select All Tasks, Import.
10. Select the Save Cert from the Desktop.
11. Select Place all Certificates in the following Store, Click Browse.
12. Check the Box that says Show Physical Stores, Expand out Trusted Root Certification Authorities, and select Local Computer there, click OK, Complete the Import.
13. Check the list to make sure it shows up. You will probably need to Refresh before you see it. Exit MMC.
14. Open Browser, select Tools, Delete Browsing History.
15. Select all but In Private Filtering Data, complete.
16. Go to Internet Options, Content Tab, Clear SSL State.
17. Close browser, then re-open and test.
You cannot download more than 50 MB or upload large files when the upload takes longer than 30 minutes using Web Client in Windows 7.
Workarounds are documented in the KB2668751 article.
Since WebDAV is an extension of HTTP, cURL can be used to script file operations.
Settings → Administration → Sharing → Allow users on this server to send shares to other servers. If this option is disabled the option –header “X-Requested-With: XMLHttpRequest” needs to be passed to cURL.
To create a folder with the current date as name:
$ curl -u user:pass -X MKCOL “https://example.com/collaboration-platform/remote.php/dav/files/USERNAME/$(date ‘+%d-%b-%Y’)”
To upload a file error.log into that directory:
$ curl -u user:pass -T error.log “https://example.com/collaboration-platform/remote.php/dav/files/USERNAME/$(date ‘+%d-%b-%Y’)/error.log”
To move a file:
$ curl -u user:pass -X MOVE –header ‘Destination: https://example.com/collaboration-platform/remote.php/dav/files/USERNAME/target.jpg’ https://example.com/collaboration-platform/remote.php/dav/files/USERNAME/source.jpg
To get the properties of files in the root folder:
$ curl -X PROPFIND -H “Depth: 1” -u user:pass https://example.com/collaboration-platform/remote.php/dav/files/USERNAME/ | xml_pp
Tue, 13 Oct 2015 17:07:45 GMT
HTTP/1.1 200 OK
Tue, 13 Oct 2015 17:07:35 GMT
HTTP/1.1 200 OK
WinSCP is an open source free SFTP client, FTP client, WebDAV client, S3 client and SCP client for Windows. Its main function is file transfer between a local and a remote computer. Beyond this, WinSCP offers scripting and basic file manager functionality.
You can download the portable version of WinSCP and run it on Linux through Wine.
To run WinSCP on Linux, download wine through your distribution’s package manager, then run it via: wine WinSCP.exe.
To connect to Collaboration platform:
Note: it is recommended to use an app password for the password if you use TOTP, as WinSCP does not understand TOTP in Collaboration platform at the time of writing (2022-11-07)
Do you like cookies?