* Extended set_config()
* Implemented get_config() which takes over $CFG loading in setup.php
* admin/auth.php has special handling if post vars starting in pluginconfig_
* admin/auth.php print_auth_lock_options() prints a form fragment -- being called from most plugins now
* user/edit.php follows the new convention when locking down fields, both javascript UI and on POST.
* admin/auth: More solid checking for auth GET/POST var.
* admin/auth: print_auth_lock_options() now handles user field mapping options for LDAP and similar modules
* admin/auth: user mapping options have moved to config_plugins table
* auth/ldap module has migrated to using new field mapping vars -- simplified config.html a lot
* auth settings migration to config_plugins
Started work with bug 2007
Bug 1969 is partacaly fixed. ldap-module supports now password expiration.
Some work with bugs 761 and 1730
Changes in login/index.php
Reordered some code to make variables reusable in multiple places.
Added redirection in case of expired password
auth_get_users ()
Returns all userobjects from external database, with userinformation
like address, phone ...
auth_sync_users ()
1. Adds users from externaldatabase to moodle.
2. renamed user in moodles db if renamed in externaldb
3. "Delete" user in moodles db if removed from externaldb
and configuration interface for guid. ;)
Course creators are managed by /admin/creator.php , same way that admins.
Or if authetication module have 'auth_iscreator'-function (right now only ldap-module have) ,
users are added to creators at login time.
Works currently only with ldap-module (tested with e-directory), but
other modules could be extended too by
adding following functions:
function auth_user_exists ($username) {
//returns true if given username already exists on authetication database
}
function auth_user_create ($userobject,$plainpass) {
//create new user to authentication database
//in inactive state (if posible)
//returns true if user is created
}
function auth_user_activate ($username) {
//activate external user after email-address is confirmed
//returns true if user is activated
}
exposes the wide array of authentication possibilities.
Authentication now has it's own page separate from other variables.
Most of this work was done by Petri Asikainen <paca@sci.fi>, who started
these changes off.
I've done some cleanups and additions which is why I'm checking it in.
It's all working pretty well at the moment but could use some testing.
Thanks, Petri! :-)
nicolasconnault