-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.9.17, 2.1, 2.2
-
Component/s: MNet
-
Labels:None
-
Testing Instructions:
-
Workaround:
-
Affected Branches:MOODLE_19_STABLE, MOODLE_21_STABLE, MOODLE_22_STABLE
-
Fixed Branches:MOODLE_19_STABLE, MOODLE_21_STABLE, MOODLE_22_STABLE
-
Pull from Repository:
-
Pull Master Branch:
-
Pull Master Diff URL:
Related to http://tracker.moodle.org/browse/MDL-27107 and http://tracker.moodle.org/browse/MDL-29991 (I can't reopen issues) the MDL-27107 and MDL-29991 patches only solves the problem when users are created into the remote host via login (auth/mnet), when users are created through the remote course enrolment process (enrol/mnet/enrol.php/enrol_user method) the users are created with 'confirmed' = 0
Steps to reproduce the problem:
1.- A Moodle 1.9 installation as identity provider publisher
2.- A Moodle 2.1 installation as identity provider subscriber
3.- On Moodle 1.9 go to frontpage administration block -> Networking -> Enrolments
4.- On Moodle 1.9 select the 2.1 subscriber host and enrol users (IMPORTANT: Users who doesn't exists in the 2.1 installation)
Result:
Users created on the Moodle 2.1 installation with the 'confirmed' field set to 0. If the Moodle 2.1 administration setting 'deleteunconfirmed' is enabled the cron will delete the no-confirmed users.
The reproduction steps are based on a real case, but watching both 1.9 and 2.x code I suspect that the problem is applicable to all branches