help logoLON-CAPA Help

An auto-update, run as a regular process, can update user information stored in LON-CAPA for all users in a domain, for whom institutional directory information is available. Which user records are updated can be controlled by institutional status (e.g., Faculty, Staff, Student etc.). If a user is affiliated with more than one group, then the attributes which can be updated will be the cumulative set for the different groups to which the user belongs.

If users are not affiliated with any institutional group, they can be accommodated within the default "Other users" group which is provided automatically. If no status types are defined for your domain, this default group is entitled "All users".

Settings for auto-update are:

In order for Autoupdate to work, the &allusers_info() routine in needs to be customized and a conduit established to institutional data. In addition, if you wish to differentiate between institutional user types in your LON-CAPA domain, you should define those in the "Institutional user types" section of the "Default authentication, language, timezone, portal, types" domain configuration screen. The types you set should be consistent with the types in use at your institution. These types are then used to populate the "User population" column in each of the "Updatable user information" row(s) in the Auto-update data table in "Domain Configuration".

Warnings will be written to the Auto-update log file found in /home/httpd/perl/logs if a possible username change is detected. Although the username is the unique identifier in LON-CAPA, the student/employee ID operates as an additional, mostly unique identifier. At present LON-CAPA does not support username changes. For users who switch username (assuming institutional authentication will no longer authenticate the user's old username) the recommendation is to convert the authentication type in LON-CAPA for the user to "internal", set an initial password, make sure that permanent e-mail is set for the user, then e-mail the user and ask them to use the "Forgot password?" link on the log-in page to change the password to something secure.