- 1 Introduction
- 2 Installation and Configuration
- 3 Troubleshooting
WebDAV is an RFC Standard for accessing and manipulating resource collections, in this case, it is used to manipulate a remote file system.
The advantage of user WebDAV is that a lot of systems implement it and on a wide variety of platforms.
WebDAV is secured by the use of passwords and can be encrypted using HTTPS.
WorkBook can store all your files on a third-party WebDAV server. This is often used to connect a hosted WorkBook with on-premises storage or storage in a branch office.
Installation and Configuration
Step 1 – Initial setup
First, you need to add the storage provider type called ‘WebDAV Storage Provider’ under Folders → Reports & Documents → Storage and Folders → Storage provider, and then insert the required configuration values.
The required values are:
- ServerRootPath: the full address including subdirectory that WorkBook should connect to (http://yourwebdav.tld/subfolder)
- WebDavUsername: User name for the WebDAV connection (this user MUST have full access to the share in question)
- WebDavPassword: The password for the WebDAV user
- DisableDepthInfinity: if you already know that the property ‘Depth Infinity’ is disabled, set this to True.
Step 2 – Test the connection
Just type a random folder name and click ‘Test’
If the WebDAV configuration is correct, all boxes in the column ‘Success’ will be ticked off.
Otherwise, see below for troubleshooting of general error message, or check the platform-specific installation instructions for troubleshooting information.
- If the test fails, you probably need to open up for one of our IP addresses in your firewall to make sure the connection is opened from our servers. These IP addresses are in use. Contact us if you’re uncertain which hosting location applies to your WorkBook.
- Australia East: 126.96.36.199
- East Asia: 188.8.131.52
- Southeast Asia: 184.108.40.206
- East US: 220.127.116.11
- Northern Europe: 18.104.22.168
Step 3 – Test from outside your network
Confirm that the WebDAV settings work from a third-party client like Cyberduck or BitKinex.
You need the following information to connect:
- Server Address (http:// or https://)
- Server Port (80, 443, etc)
- Password (*********)
Confirm that you can do the following actions:
- List content
- Create directory
- Delete directory
- Upload file
- Delete file
Known limitations: WorkBook does not support directories with leading or trailing white spaces.
List folder content returns 400 Bad Request or 403 Forbidden
These status codes will normally indicate that we tried to use Depth Infinity but that was not allowed.
On Apache, it might indicate that the WebDAV User lacks permissions to one or more files/folders.
Ensure that the Username and Password are correct, note that the password often comes before username in the setup grid.
Make sure that the server is actually requesting basic authentication, you can see this by looking at the authentication respond a WebDAV client sends.
The header should look like this: “Authorization: Basic…”
When uploading a receiving a 404 Not Found
If you are using Internet Information Service this error indicates that you are trying to upload a file that is larger than the maximum allowed size.
The default limit is 30 megabytes, see Internet Information Service Step 5 for information on how to modify the limit.
If you’re using Apache with mod_dav try and enable “UseStreamingUpload” on the storage provider, this will allow WorkBook to upload the file in multiple chunks.
Nothing happens when I change the setting
See Common Known Issues for more information.
Could not create SSL/TLS secure channel
If WorkBook reports the error ‘Could not create SSL/TLS secure channel’ when attempting to connect with the WebDAV storage, it is most likely because the server and client is unable to negotiate an SSL/TLS Session.
There is a known incompatibility with newer versions of OSX and WorkBook (prior to 22.214.171.124), as OSX only has TLS 1.2 enabled by default and WorkBook only supports TLS 1.0 and 1.1
TLS 1.1 can be re-enabled on OSX if you modify the apache service proxy configuration file, see the following article.