Annotation of loncom/html/adm/help/tex/Domain_Configuration_Quotas.tex, revision 1.8
1.1 raeburn 1: \label{Domain_Configuration_Quotas}
1.2 raeburn 2: By default, each user in your domain can create blogs, a personal
3: information page, and store files in an individual portfolio space.
4: Students can submit items from their portfolio to meet the requirements
5: of assignments in their courses.
1.1 raeburn 6:
1.2 raeburn 7: You can choose to disable personal information pages, blogs and/or portfolios
8: for different groups of users defined for your domain (e.g., Faculty, Adjunct,
9: Staff, Student). If the ``Modify User'' utility in User Management is
10: used to explicitly set availability of these tools for a particular user,
11: that will override the corresponding settings determined by the user's
12: affiliation.
13:
1.3 raeburn 14: If you choose to enable portfolios, default quotas (in MB)
1.2 raeburn 15: can similarly be set to vary by institutional affiliation.
1.1 raeburn 16: If a user is affiliated with more than one group, whichever default
17: quota is largest for the different groups is the one which applies.
1.3 raeburn 18: Institutional types are defined in the ``Institutional user types''
1.4 raeburn 19: section on the ``Default authentication, language, timezone, portal, types''
1.3 raeburn 20: screen. If no types have been defined, then a single default quota
21: will apply for all users from the domain.
1.2 raeburn 22:
23: Default portfolio quotas which can be set for users in your domain
24: will be overridden by any quota you set for an individual user via:
25: the ``Modify User'' utility.
1.3 raeburn 26:
27: Additional options for authoring spaces can be set for the various user
28: types: (a) whether webDAV is active, and (b) the default quota for Authoring Space.
29: These only come into effect for a particular user, when an author and/or one or
30: more co-author roles have been assigned to a user to provide access to one or more
31: Authoring Spaces.
32:
33: WebDAV allows a user to connect to an Authoring Space in the same way as removable
34: media, and to use their own laptop/desktop computer's file management tools and
1.5 raeburn 35: applications to move, edit and delete files. See: ``WebDAV access to Authoring Space''
36: section in the Authoring manual for more information.
37:
1.4 raeburn 38: Note: webDAV usage requires Apache with SSL to be running on the library server.
1.6 raeburn 39: The user will be prompted to enter his/her username (this will be the LON-CAPA username
40: or username,domain if the access is for a co-author with a domain different
1.7 raeburn 41: to that of the author), and the user's LON-CAPA password. webDAV also requires that the
1.8 ! raeburn 42: dav and dav\_fs modules are enabled in Apache. The way those are enabled depends on the
1.7 raeburn 43: Linux distro (command line access required).
44: the Apache config.
45:
46: \begin{itemize}
47:
48: \item CentOS, Red Hat and Scientific Linux (6 and earlier)
49:
50: The required LoadModule lines are included in the /etc/httpd/conf/httpd.conf
51: file added by install.pl run to prepare a server for installation of LON-CAPA.
52:
53: \item CentOS, Red Hat and Scientific Linux 7
54:
55: The required LoadModule lines are in the default /etc/httpd/conf.modules.d/00-dav.conf
56: file added when the httpd rpm is installed.
57:
58: \item Ubuntu
59:
1.8 ! raeburn 60: Use the commands: a2enmod dav and a2enmod dav\_fs to enable the modules.
1.7 raeburn 61:
62: \item SLES
63:
1.8 ! raeburn 64: The APACHE\_MODULES entry in /etc/sysconfig/apache2 contains the list of modules to be
! 65: loaded. If dav and dav\_fs are not present they should be added to the list.
1.7 raeburn 66:
67: \end{itemize}
68:
69: (Reload Apache after making any changes to the Apache configuration).
1.5 raeburn 70:
71: If you use Single Sign On to authenticate LON-CAPA users in your domain, then to
72: support webDAV you also need to support authentication by LON-CAPA for your users.
73: This can achieved if the authentication type stored internally for each SSO user is
74: set to either (a) Kerberos 5 (with a parameter -- the appropriate Kerberos realm
75: set), or (b) Local Authentication, with /home/httpd/lib/perl/localauth.pm
76: customized to verify username and password (e.g., via LDAP). If a user can log-in
77: to LON-CAPA via the URL /adm/login (thereby by-passing SSO), then the same user will
78: also be able to authenticate using a WebDAV client (assuming other requirements are
79: met, i.e., SSL, WebDAV access enabled, active author or co-author role).
1.3 raeburn 80:
81: The requirement to obsolete published files before moving or deleting them, which applies to
82: the regular web browser-based management of Authoring Space, also applies in the webDAV
83: environment. Moving and deleting directories in the webDAV environment is prohibited if
84: the directory, or any (nested) subdirectory contains a non-obsolete published resource.
85:
86: Given the ability to easily delete unpublished content in webDAV (without the ability to
87: reverse the deletion), it is important that authors assigned webDAV access are especially
88: careful when working in the webDAV environment.
89:
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>