Annotation of loncom/html/adm/help/tex/Domain_Configuration_Auto_Updates.tex, revision 1.4
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
6: etc.). If a user is affiliated with more than group, then the attributes
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.1 raeburn 11: be accommodated within the default \char`\"{}Other users\char`\"{}
12: group which is provided automatically. If no status types are defined
13: for your domain, this default group is entitled \char`\"{}All users\char`\"{}.
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.
! 22: \item Set whether users with a particular status (e.g., Faculty, Staff,
! 23: Student etc.) should have access to a user preference which permits them
! 24: to lock their existing user information, and disable automatic updates
! 25: of their own information, should it change in the institutional directory.
! 26: Note: this option is only shown if institutional groups have been defined.
1.1 raeburn 27: \item Set which of the following attributes: first name, middle name, last
28: name, generation, e-mail address, student/employee ID should be updated
29: within LON-CAPA if a different version to the one currently stored
30: is retrieved from the institutional directory.
31: \end{itemize}
32: In order for Autoupdate to work, the \&allusers\_info() routine in
33: localenroll.pm needs to be customized and a conduit established to
34: institutional data. In addition, if you wish to differentiate between
35: institutional user types in your LON-CAPA domain the \&inst\_usertypes()
36: routine in localenroll.pm will need to be customized to correspond
37: with the types used at your institution. These types are then used
38: to populate the \char`\"{}User population\char`\"{} column in each
39: of the \char`\"{}Updateable user information\char`\"{} row(s) in the
40: Auto-update data table in \char`\"{}Domain Configuration\char`\"{}.
41:
42: Warnings will be written to the Auto-update log file found in /home/httpd/perl/logs
43: if a possible username change is detected. Although the username is
44: the unique identifier in LON-CAPA, the student/employee ID operates
45: as an additional, mostly unique identifier. At present LON-CAPA does
46: not support username changes. For users who switch username (assuming
47: institutional authentication will no longer authenticate the user's
1.2 raeburn 48: old username) the recommendation is to convert the authentication type
49: in LON-CAPA for the user to \char`\"{}internal\char`\"{}, set an
50: initial password, make sure that permanent e-mail is set for the user,
51: then e-mail the user and ask them to use the
52: \char`\"{}\underbar{Forgot password?}\char`\"{} link on the log-in page
53: to change the password to something secure.
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>