Difference between revisions of "WebDAV"
(Created page with "= Introduction = The DAV module is the key of adding a WebDAV server to Tactic and it can be accessed with any WebDAV client effortlessly. Both of a public and private directory can be offered. For the shared public directory, you will not be needing log-in credentials. However, for the private directory the log-in credentials of Tactic is required. With the help of the private directory the content of manual directory or ECM or DMS module can be accessed as well. = Inst...") |
|||
| Line 7: | Line 7: | ||
The private directory that is protected by a log-in is associated with a HTTP Basic authentication. Hence, if the Tactic directory is already protected with HTTP Basic authentication protection the path of path */dav* needs to be excluded. Exclusion of the path will prevent the duplication of HTTP Basic authentication. For an example, if you have protected your directory with the help of | The private directory that is protected by a log-in is associated with a HTTP Basic authentication. Hence, if the Tactic directory is already protected with HTTP Basic authentication protection the path of path */dav* needs to be excluded. Exclusion of the path will prevent the duplication of HTTP Basic authentication. For an example, if you have protected your directory with the help of | ||
<Directory "/my-path-to-my-tactic-hdocs"> | <Directory "/my-path-to-my-tactic-hdocs"> | ||
AuthType Basic | AuthType Basic | ||
AuthName "Restricted Files - HTTP Basic protection on Tactic" | AuthName "Restricted Files - HTTP Basic protection on Tactic" | ||
AuthUserFile "/pathtohttpbasicpasswords" | AuthUserFile "/pathtohttpbasicpasswords" | ||
Require user ahttpbasiclogin | Require user ahttpbasiclogin | ||
</Directory> | </Directory> | ||
An exclusion like this one must be added, hence, the DAV features will be using the HTTP Basic embedded into the DAV component instead of using the generic basic HTTP protection. | An exclusion like this one must be added, hence, the DAV features will be using the HTTP Basic embedded into the DAV component instead of using the generic basic HTTP protection. | ||
<Directory "/my-path-to-my-tactic-hdocs/dav"> | <Directory "/my-path-to-my-tactic-hdocs/dav"> | ||
Require all granted | Require all granted | ||
</Directory> | </Directory> | ||
= Usage of the module = | = Usage of the module = | ||
The WebDAV root URL can be found on the setup page, which can be accessed by any WebDAV client. It needs to be noted that all the enabled WebDAV directories are the subordinates of the root URL. | The WebDAV root URL can be found on the setup page, which can be accessed by any WebDAV client. It needs to be noted that all the enabled WebDAV directories are the subordinates of the root URL. | ||
Revision as of 11:32, 6 July 2022
Introduction
The DAV module is the key of adding a WebDAV server to Tactic and it can be accessed with any WebDAV client effortlessly. Both of a public and private directory can be offered. For the shared public directory, you will not be needing log-in credentials. However, for the private directory the log-in credentials of Tactic is required. With the help of the private directory the content of manual directory or ECM or DMS module can be accessed as well.
Installation
There is no need of installing this module, as it is already included within Tactic services. Setup For using this module the users need to enable it by using an administrator account. The menu options for activating this module are: Home –> Setup – > Module. The users then need to click on Activate. The modules will be activated after completing this step. The settings icon will be visible at the end of the module box, the users can click in that to access setup. The private directory that is protected by a log-in is associated with a HTTP Basic authentication. Hence, if the Tactic directory is already protected with HTTP Basic authentication protection the path of path */dav* needs to be excluded. Exclusion of the path will prevent the duplication of HTTP Basic authentication. For an example, if you have protected your directory with the help of
<Directory "/my-path-to-my-tactic-hdocs"> AuthType Basic AuthName "Restricted Files - HTTP Basic protection on Tactic" AuthUserFile "/pathtohttpbasicpasswords" Require user ahttpbasiclogin </Directory>
An exclusion like this one must be added, hence, the DAV features will be using the HTTP Basic embedded into the DAV component instead of using the generic basic HTTP protection.
<Directory "/my-path-to-my-tactic-hdocs/dav"> Require all granted </Directory>
Usage of the module
The WebDAV root URL can be found on the setup page, which can be accessed by any WebDAV client. It needs to be noted that all the enabled WebDAV directories are the subordinates of the root URL.
