Return to Domain_Configuration_Quotas.tex CVS log

Up to [LON-CAPA] / loncom / html / adm / help / tex

- Update documentation.
  - webDAV authentication: separator between username and domain is a comma
    (domain only required for co-authors from a different domain).

    1: \label{Domain_Configuration_Quotas}
    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.
    6: 
    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: 
   14: If you choose to enable portfolios, default quotas (in MB) 
   15: can similarly be set to vary by institutional affiliation.
   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.
   18: Institutional types are defined in the ``Institutional user types''
   19: section on the ``Default authentication, language, timezone, portal, types'' 
   20: screen. If no types have been defined, then a single default quota
   21: will apply for all users from the domain.
   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.
   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
   35: applications to move, edit and delete files. See: ``WebDAV access to Authoring Space''
   36: section in the Authoring manual for more information.
   37: 
   38: Note: webDAV usage requires Apache with SSL to be running on the library server.  
   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 
   41: to that of the author), and the user's LON-CAPA password. 
   42: 
   43: If you use Single Sign On to authenticate LON-CAPA users in your domain, then to
   44: support webDAV you also need to support authentication by LON-CAPA for your users.
   45: This can achieved if the authentication type stored internally for each SSO user is 
   46: set to either (a) Kerberos 5 (with a parameter --  the appropriate Kerberos realm 
   47: set), or (b) Local Authentication, with /home/httpd/lib/perl/localauth.pm
   48: customized to verify username and password (e.g., via LDAP).  If a user can log-in  
   49: to LON-CAPA via the URL /adm/login (thereby by-passing SSO), then the same user will 
   50: also be able to authenticate using a WebDAV client (assuming other requirements are 
   51: met, i.e., SSL, WebDAV access enabled, active author or co-author role).
   52: 
   53: The requirement to obsolete published files before moving or deleting them, which applies to
   54: the regular web browser-based management of Authoring Space, also applies in the webDAV 
   55: environment. Moving and deleting directories in the webDAV environment is prohibited if
   56: the directory, or any (nested) subdirectory contains a non-obsolete published resource.
   57: 
   58: Given the ability to easily delete unpublished content in webDAV (without the ability to 
   59: reverse the deletion), it is important that authors assigned webDAV access are especially
   60: careful when working in the webDAV environment. 
   61: