File:
[LON-CAPA] /
loncom /
html /
adm /
help /
tex /
Domain_Configuration_Auto_Updates.tex
Revision
1.3:
download - view:
text,
annotated -
select for diffs
Tue Sep 29 12:54:54 2009 UTC (14 years, 10 months ago) by
bisitz
Branches:
MAIN
CVS tags:
version_2_9_99_0,
version_2_10_0_RC2,
version_2_10_0_RC1,
bz6209-base,
bz6209,
PRINT_INCOMPLETE_base,
PRINT_INCOMPLETE,
HEAD,
GCI_3
Correction: It's auto-update, not auto-enrollment
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:
10: If users are not affilliated with any institutional group, they can
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}
18: \item Set auto-update as active or inactive in the domain.
19: \item Set whether user information changes should propagate to data stored
20: in classlist database files for the separate courses in which the
21: user has an active student role.
22: \item Set which of the following attributes: first name, middle name, last
23: name, generation, e-mail address, student/employee ID should be updated
24: within LON-CAPA if a different version to the one currently stored
25: is retrieved from the institutional directory.
26: \end{itemize}
27: In order for Autoupdate to work, the \&allusers\_info() routine in
28: localenroll.pm needs to be customized and a conduit established to
29: institutional data. In addition, if you wish to differentiate between
30: institutional user types in your LON-CAPA domain the \&inst\_usertypes()
31: routine in localenroll.pm will need to be customized to correspond
32: with the types used at your institution. These types are then used
33: to populate the \char`\"{}User population\char`\"{} column in each
34: of the \char`\"{}Updateable user information\char`\"{} row(s) in the
35: Auto-update data table in \char`\"{}Domain Configuration\char`\"{}.
36:
37: Warnings will be written to the Auto-update log file found in /home/httpd/perl/logs
38: if a possible username change is detected. Although the username is
39: the unique identifier in LON-CAPA, the student/employee ID operates
40: as an additional, mostly unique identifier. At present LON-CAPA does
41: not support username changes. For users who switch username (assuming
42: institutional authentication will no longer authenticate the user's
43: old username) the recommendation is to convert the authentication type
44: in LON-CAPA for the user to \char`\"{}internal\char`\"{}, set an
45: initial password, make sure that permanent e-mail is set for the user,
46: then e-mail the user and ask them to use the
47: \char`\"{}\underbar{Forgot password?}\char`\"{} link on the log-in page
48: to change the password to something secure.
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>