Webdav and REST in OpenKM CE 7.0

[wpmproductions]

Hi,

I was very pleased to see that the OpenKM CE version 7.0 is available. I have installed and configured it on a windows server 2025 server an got it directly working.

I was planning to use webdav and/or REST. On the comparison of versions page it says that webdav and REST are available in the CE version.

Is there something I have to install to enable webdav and/or REST?

Kind regards,
WPMProductions

[jllort]

REST comes by default; really, the UI uses REST requests for everything.

About WEBDAV, because of security issues with the libraries, we have removed it.

[hcq]

Hi,

I was using WebDAV with Mountain Duck to mount my OpenKM 6.3 CE repository as a network drive in Finder on macOS. This worked great for direct file access without using the web interface.

Since WebDAV has been removed in OpenKM 7 CE due to security issues, I am looking for an alternative solution to achieve the same result — mounting OpenKM documents directly in macOS Finder.

Is there any supported way to do this with OpenKM 7 CE? For example:
- A REST-based mount option
- A compatible client that works with the OpenKM REST API
- Any other recommended approach

Thanks in advance.

Hans-Christoph

[jllort]

We regret that you were using this functionality, but it has been removed and we have no plans whatsoever to reinstate it for several reasons:
* The age of the libraries poses a serious security issue, so it is not possible to continue using them directly within the project.
* At the time, we were in contact with the developer of these libraries, who requested $3–4K per OpenKM instance to include updated libraries (that is, the base project that was originally incorporated at no cost as part of the document manager disappeared, making its use unviable for both Professional and CE version users. No one was willing to assume this cost per instance).
* At one point, we also tried incorporating some CIFS libraries, which worked but had terrible performance, so they were also discarded.
* Ultimately, exposing a document management system as a mount point is bad practice for several reasons (security is lost in certain critical actions, such as deleting or moving nodes, which a user can perform unintentionally from a mapped drive, whereas this is not possible within a controlled graphical environment; junk files are created because some users edit directly on these types of drives, etc.). It is a feature we have always regretted adding, which we recommended not using, but that some users insisted on using (the security issues have provided an opportunity to remove it).

The only thing allowed is an FTP connection; I am not sure whether it is possible to mount a virtual drive using this protocol. However, I would not recommend it either in our document management system or in any other; in our view, this functionality goes completely against a secure document management model.