Configuring WebDAV

WebDAV integration provides access to the file system on the staging server similar to FTP/SFTP and can be used in lieu of FTP/SFTP. WebDAV (Web Distributed Authoring and Versioning) is a communications protocol that honors settings in OU Campus. Unlike FTP/SFTP, when file management is performed using WebDAV, OU Campus treats the files as if they were being managed via the OU Campus interface.

Advantages of WebDAV over FTP is that FTP does not connect to the OU Campus database. File management is not integrated with OU Campus when using FTP. WebDAV implementation allows the files to be tied into OU Campus functionality. This includes permissions/access control, checking files in and out, renaming, adding, deleting, etc. WebDAV functionality (aka verbs) such as rename, delete, get, and put work seamlessly with OU Campus.

Once WebDAV is enabled at the account and site level by a Super Admin or by the OU Campus Support team, Level 10 administrators can allow access for users with authority levels 9 and 10. Once enabled in OU Campus, a WebDAV client can be used to connect to the staging server.

File Management

When using WebDAV with OU Campus the following file management actions honored include (but are not limited to):

  • Permissions/access control
  • Checking in and out files
  • Updating files
  • Editing and saving changes to files
  • Uploading files and directories
  • Moving files and directories
  • Downloading files and directories
  • Deleting files and directories
  • Creating files and directories
  • Renaming files and directories
  • Dependency tag management

Note: Asset files are not accessible for editing via WebDAV.

Authentication Methods

The various current methods of authenticating log in credentials are supported. This includes LDAP, CAS, Shibboleth, and OU Campus login. Once the administrator has set up LDAP and/or OU Campus users, WebDAV can be used. For CAS and Shibboleth, the user must set a password for use with WebDAV in order to log in to the OU Campus system via a WebDAV client. This is a separate password than is used with CAS and Shibboleth logins to OU Campus.

Enabling WebDAV

Authority Level: Super Admin

For most OU Campus implementations, the administrator will need to contact OU Campus Support to request to have WebDAV enabled. Otherwise, WebDAV can be enabled at the Super Admin account level, and must be enabled for both the account and for each site under the account. Level 10 administrators can then configure access for users with authority levels 9 and 10. 

Enable WebDAV for the Account

  1. From the Super Admin interface for the accounts listing, click Edit.

  2. Under General Settings > Optional Features > Enable WebDAV.

Enabling WebDAV

3. Select the Enable WebDAV option and click Update.

Enable WebDAV for Each Site

  1. From the Site listing under the Super Admin interface, click Edit.

  2. Under the WebDAV section, select the Enable WebDAV checkbox.

Enabling WebDAV for the Site

Allowing WebDAV Access for a User

Authority Level: Administrator Level 10

1. Navigate to Setup > Users > WebDAV Configuration and Access section (This is only available after WebDAV is activated at the Super Admin Account level.)

2. Select the Allow WebDAV access checkbox. This allows for file access to the staging server. If using OU Campus authentication, the password is the same as what is used to login to OU Campus. If LDAP is used, the LDAP password is used with the WebDAV client. If CAS and Shibboleth are used, a new WebDAV-specific password must be set in the Users settings screen to allow access via WebDAV. WebDAV access to OU Campus does not use CAS and Shibboleth authentication.

3. Note the WebDAV URL. This is used when configuring settings for the WebDAV client. The WebDAV URL listed in this section is the path to the account, not the site. A specific site or folder can be appended to it and used for the WebDAV client configuration.

Enabling WebDAV for a User

Supported Clients

The integration of WebDAV into OU Campus supports a number of WebDAV clients. While it isn't feasible to test every possible client and platform combination, the following clients have been tested:

  • <oXygen/> XML Editor 14.2 (both Windows and Mac)
  • Dreamweaver C6 (Web development, both Windows and Mac)
  • BitKinex 3.2 (FTP/SFTP/WebDAV client, Windows)
  • Transmit 4 (FTP/SFTP/WebDAV client, Mac)
  • Coda 2 (FTP/SFTP/WebDAV client, Mac)
  • Interarchy 10 (FTP/SFTP/WebDAV client, Mac)
  • Mac OS X 10.8 Finder (Mac)

Clients with File Locking Support

The following clients have been tested and are known to support file locking (check in/check out):

  • <oXygen/> XML Editor (both Windows and Mac)
  • Dreamweaver (both Windows and Mac)
  • BitKinex (Windows)

Clients without File Locking Support

The following clients have been tested and are known to not support file locking (check in/check out):

  • Transmit 4 (Mac)
  • Coda 2 (Mac)
  • Interarchy 10 (Mac)
  • Mac OS X 10.8 Finder (Mac)

Example Setup (Cyberduck)

  1. Click Open Connection.
  2. Select WebDAV (Web-based Distributed Authoring and Versioning) from the drop-down.
  3. For the Server field, enter the WebDAV URL noted previously. That is, the path specified from Setup > Users > WebDAV section > WebDAV URL.
  4. Clear the Anonymous Login checkbox.
  5. Enter Username and Password.
  6. Click Connect.

Cyberduck Setup Screen

WebDAV Setup


1. When troubleshooting connection errors, note that WebDAV must be enabled by a Super Admin for both the account and each site, as well as for the admin user. If not enabled at one of these levels, the WebDAV client will not be able to connect.

2. Use extreme caution when granting staging server access as an administrator is able to delete both a site record from the database as well as the site files from the staging server.

3. Users may need to refresh their browser windows in both OU Campus and the WebDAV client to see changes made by one or the other, if both are active at the same time.

Moving Files and Folders

  1. Files and folders are able to be moved only within the WebDAV enabled site.
  2. Moving files across sites is not supported. (One alternative to be considered is copying files to a local computer and then to the desired site.)

Naming and Renaming

  1. Naming and renaming a file WILL NOT conform to the site′s pre-defined regex settings.
  2. Special characters are permitted upon upload and renaming file or folders. Users need to be careful as some special characters can cause OU Campus to stop responding to the file. Error behavior in this case can include preview and rename not functioning. If a problem character is present in a file that was uploaded or renamed via a WebDAV client into OU Campus, the user needs to use the WebDAV client to rename the file.


  1. Uploading non-binary files (text) via WebDAV is permitted.
  2. Uploading binary files via WebDAV to the OU Campus staging server is not permitted. This restriction will be removed when Binary Management is released.


  1. The WebDAV client (that supports locking) checks out the file to the user in OU Campus.
  2. If a file is checked out to another user in OU Campus, then the file is locked to the WebDAV client, the client will not be able to edit it but can view a ″Read-Only″ copy of the file.
  3. OU Campus can override locks that are initiated by a WebDAV client. When this occurs, the corresponding WebDAV client still holds the lock even though it is now invalid. However, OU Campus correctly denies access if the WebDAV client tries to act on the (now invalidly locked) file. An exception to this is that Dreamweaver allows a lock override.

CAS and Shibboleth

The log-in system via CAS and Shibboleth bypasses the internal authentication system in OU Campus. As a result, CAS and Shibboleth based authentication is not compatible with the OU Campus WebDAV authentication. In this case, an OU Campus password needs to be added when activating WebDAV for a user, so that the user can log-in via WebDAV. The password can be added in the Setup > Users > Edit, and is independent of the CAS and Shibboleth password.  

Was this page helpful?

Additional Comments:

(Include your email address if you would like a reply)

Procede to