Annotation of loncom/html/adm/help/tex/Domain_Configuration_Auto_Updates.tex, revision 1.10
1.1 raeburn 1: \label{Domain_Configuration_Auto_Updates}
2: An auto-update, run as a regular process, can update user information
3: stored in LON-CAPA for all users in a domain, for whom institutional
4: directory information is available. Which user records are updated
5: can be controlled by institutional status (e.g., Faculty, Staff, Student
1.5 bisitz 6: etc.). If a user is affiliated with more than one group, then the attributes
1.1 raeburn 7: which can be updated will be the cumulative set for the different
8: groups to which the user belongs.
9:
1.4 raeburn 10: If users are not affiliated with any institutional group, they can
1.9 raeburn 11: be accommodated within the default ``Other users''
1.1 raeburn 12: group which is provided automatically. If no status types are defined
1.9 raeburn 13: for your domain, this default group is entitled ``All users''.
1.1 raeburn 14:
15: Settings for auto-update are:
16:
17: \begin{itemize}
1.3 bisitz 18: \item Set auto-update as active or inactive in the domain.
1.1 raeburn 19: \item Set whether user information changes should propagate to data stored
20: in classlist database files for the separate courses in which the
1.4 raeburn 21: user has an active student role.
1.10 ! raeburn 22: \item Set whether to skip updates for users without active or future roles.
! 23: \item Set whether to skip updates for users for whom the last modification
! 24: to the activity log is more than a specified threshold (in days), and the
! 25: time since the last role assignment change also exceeds the same threshold.
1.4 raeburn 26: \item Set whether users with a particular status (e.g., Faculty, Staff,
27: Student etc.) should have access to a user preference which permits them
28: to lock their existing user information, and disable automatic updates
29: of their own information, should it change in the institutional directory.
30: Note: this option is only shown if institutional groups have been defined.
1.1 raeburn 31: \item Set which of the following attributes: first name, middle name, last
32: name, generation, e-mail address, student/employee ID should be updated
33: within LON-CAPA if a different version to the one currently stored
34: is retrieved from the institutional directory.
35: \end{itemize}
36: In order for Autoupdate to work, the \&allusers\_info() routine in
37: localenroll.pm needs to be customized and a conduit established to
38: institutional data. In addition, if you wish to differentiate between
1.7 raeburn 39: institutional user types in your LON-CAPA domain, you should define
40: those in the ``Institutional user types'' section of the
1.8 raeburn 41: ``Default authentication, language, timezone, portal, types''
1.7 raeburn 42: domain configuration screen. The types you set should be consistent with the
43: types in use at your institution. These types are then used to populate
1.9 raeburn 44: the ``User population'' column in each of the
45: {}``Updatable user information'' row(s) in the
46: Auto-update data table in {}``Domain Configuration''.
1.1 raeburn 47:
48: Warnings will be written to the Auto-update log file found in /home/httpd/perl/logs
49: if a possible username change is detected. Although the username is
50: the unique identifier in LON-CAPA, the student/employee ID operates
51: as an additional, mostly unique identifier. At present LON-CAPA does
52: not support username changes. For users who switch username (assuming
53: institutional authentication will no longer authenticate the user's
1.2 raeburn 54: old username) the recommendation is to convert the authentication type
1.9 raeburn 55: in LON-CAPA for the user to ``internal'', set an
1.2 raeburn 56: initial password, make sure that permanent e-mail is set for the user,
57: then e-mail the user and ask them to use the
1.9 raeburn 58: ``\underbar{Forgot password?}'' link on the log-in page
1.2 raeburn 59: to change the password to something secure.
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>