Protocols
LogicalDOC normally uses the HTTP or HTTPS protocols but it also implements additional protocols you might want to control in the Protocols section.
|
Additional protocols implemented by LogicalDOC |
||
|---|---|---|
| Protocol | Description | Configuration |
| WebService | Used for programmatically interacting with LogicalDOC from a 3rd party application. See more here. |
Enabled: enables or disables this protocol Enable Basic Authentication: enables the legacy authentication that uses username and password (less secure) Record calls: records all the calls to the API (enable with care, it may stress the system) Record calls payload: also save the payload in the API records (enable with care, it may stress the system) Time to live: number of days an API record can stay in the system before being deleted |
| CMIS | Content Management Interoperability Services (CMIS) is an open standard that allows different content management systems to inter-operate over the Internet. |
Enabled: enables or disables this protocol Change Log: if enabled, the client can obtain the last events happened since a given date Max items: maximum number of elements returned when the client asks for the change log |
| WebDAV | Web-based Distributed Authoring and Versioning is a long-standing protocol that enables a webserver to act as a fileserver and support collaborative authoring of content on the web. |
Enabled: enables or disables this protocol Depth: maximum depth of preventive introspection |
| FTP | The File Transfer Protocol (FTP) is a standard network protocol used for the transfer of computer files between a client and server on a computer network. |
Enabled: enables or disables this protocol Port: the working port Encryption(FTPS): if you want the FTPS encrypted protocol instead of the standard FTP Key Store: the path where it is located the Java Key Store that contains your certificate Key Store alias: alias of the certificate to use Key Store password: password to access the Key Store |