-
Bug
-
Resolution: Fixed
-
Major
-
1.9.2, 2.0, 2.1, 2.2
-
None
-
This was discovered using Moodle on an Ubuntu server, though I doubt the issue is related to the environment.
-
MySQL
-
MOODLE_19_STABLE, MOODLE_20_STABLE, MOODLE_21_STABLE, MOODLE_22_STABLE
-
MOODLE_19_STABLE, MOODLE_20_STABLE, MOODLE_21_STABLE
-
wip_
MDL-16168_HEAD_CAS_crash_if_no_LDAP
After configuring CAS on a fresh Moodle install and updating the mdl_user table with:
update mdl_user set auth='cas';
we get successfully redirected on login to the CAS server and back to Moodle as we would expect.
However, it then returns an error about not being able to connect to the LDAP server. We aren't using LDAP, and we didn't configure Moodle to use LDAP, so that would be a bug.
The patch that we made to work around the bug was to comment out the calls to update_user_record and create_user_record that are found in lib/moodlelib.php. It would be better if Moodle recognized that we were not using LDAP and that it wouldn't try to update or create users in that case.
