--- loncom/html/adm/help/tex/Domain_Configuration_Quotas.tex 2014/06/26 15:07:10 1.3 +++ loncom/html/adm/help/tex/Domain_Configuration_Quotas.tex 2020/01/10 17:24:42 1.8 @@ -16,7 +16,7 @@ can similarly be set to vary by institut If a user is affiliated with more than one group, whichever default quota is largest for the different groups is the one which applies. Institutional types are defined in the ``Institutional user types'' -section on the ``Default authentication/language/timezone/portal/types'' +section on the ``Default authentication, language, timezone, portal, types'' screen. If no types have been defined, then a single default quota will apply for all users from the domain. @@ -32,14 +32,51 @@ Authoring Spaces. WebDAV allows a user to connect to an Authoring Space in the same way as removable media, and to use their own laptop/desktop computer's file management tools and -applications to move, edit and delete files. In the case of MacOS, the user selects -the ``Go'' item in the Finder toolbar and selects ``Connect to Server''. -The user will then enter a URL for a library server where the authoring space is located: -e.g., https://s10.lite.msu.edu/webdav/msu/sparty/ where msu is the domain and sparty -is the username of the Authoring Space. Note: webDAV usage requires Apache/SSL to be -running on the library server. The user will be prompted to enter a username -(this will be the LON-CAPA username, if the user is also the author, or username:domain -of the user, if the access is for a co-author), and the user's LON-CAPA password. +applications to move, edit and delete files. See: ``WebDAV access to Authoring Space'' +section in the Authoring manual for more information. + +Note: webDAV usage requires Apache with SSL to be running on the library server. +The user will be prompted to enter his/her username (this will be the LON-CAPA username +or username,domain if the access is for a co-author with a domain different +to that of the author), and the user's LON-CAPA password. webDAV also requires that the +dav and dav\_fs modules are enabled in Apache. The way those are enabled depends on the +Linux distro (command line access required). +the Apache config. + +\begin{itemize} + +\item CentOS, Red Hat and Scientific Linux (6 and earlier) + +The required LoadModule lines are included in the /etc/httpd/conf/httpd.conf +file added by install.pl run to prepare a server for installation of LON-CAPA. + +\item CentOS, Red Hat and Scientific Linux 7 + +The required LoadModule lines are in the default /etc/httpd/conf.modules.d/00-dav.conf +file added when the httpd rpm is installed. + +\item Ubuntu + +Use the commands: a2enmod dav and a2enmod dav\_fs to enable the modules. + +\item SLES + +The APACHE\_MODULES entry in /etc/sysconfig/apache2 contains the list of modules to be +loaded. If dav and dav\_fs are not present they should be added to the list. + +\end{itemize} + +(Reload Apache after making any changes to the Apache configuration). + +If you use Single Sign On to authenticate LON-CAPA users in your domain, then to +support webDAV you also need to support authentication by LON-CAPA for your users. +This can achieved if the authentication type stored internally for each SSO user is +set to either (a) Kerberos 5 (with a parameter -- the appropriate Kerberos realm +set), or (b) Local Authentication, with /home/httpd/lib/perl/localauth.pm +customized to verify username and password (e.g., via LDAP). If a user can log-in +to LON-CAPA via the URL /adm/login (thereby by-passing SSO), then the same user will +also be able to authenticate using a WebDAV client (assuming other requirements are +met, i.e., SSL, WebDAV access enabled, active author or co-author role). The requirement to obsolete published files before moving or deleting them, which applies to the regular web browser-based management of Authoring Space, also applies in the webDAV