Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-40243

LDAP cron synchronization script not suspending user

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Minor Minor
    • 2.6
    • 2.3.7, 2.4.4, 2.5
    • Authentication
    • MOODLE_23_STABLE, MOODLE_24_STABLE, MOODLE_25_STABLE
    • MOODLE_26_STABLE
    • w28_MDL-40243_m26_ldapsuspend
    • Hide

      1/ configure test openldap - see http://docs.moodle.org/dev/PHPUnit_installation_in_OS_X#Install_and_configure_OpenLDAP
      2/ make sure MDL-40346 was already integrated, otherwise you get notice during test execution
      3/ run phpunit tests (make sure auth_ldap tests are not skipped!)

      These testing instructions assume that we already have a LDAP server setup with external users (at least one), and that we have correctly configured the LDAP authentication plugin to talk to the LDAP server.

      1. Set Authentication > LDAP > cron synchronization script > Removed ext user to "Suspend internal".
      2. Without applying the fix, run the auth/ldap/cli/sync_users.php script from the command line.
      3. Check that all the LDAP users are created/updated correctly in Moodle, and that all of them appear as 'enabled'.
      4. Remove an existing user in the LDAP server and re-run the sync.php script.
      5. Check that the Moodle internal user still appears as 'enabled' (but has 'nologin' as the authentication method).
      6. Check that the user can't login (even if it appears as 'enabled')
      7. Re-create the external user in the LDAP server and re-run the sync.php.
      8. Check that the Moodle internal user is 'revived', i.e., it appears as 'enabled' and has 'ldap' as the authentication method.
      9. Check that the user can login again and the user course data (grades, etc.) are still there.
      10. Remove the existing user in the LDAP server again.
      11. Now apply the fix and re-run the sync.php script.
      12. Check that the same Moodle internal user now appears as 'disabled' (aswell as having the 'nologin' authentication method).
      13. Check that the user can't login.
      14. Now re-create the external user in the LDAP server and re-run the sync script.
      15. Check that the Moodle internal user is 'revived', i.e., it appears as 'enabled' and has 'ldap' as the authentication method.
      16. Check that the user can login again and the user course data (grades, etc.) are still there.
      Show
      1/ configure test openldap - see http://docs.moodle.org/dev/PHPUnit_installation_in_OS_X#Install_and_configure_OpenLDAP 2/ make sure MDL-40346 was already integrated, otherwise you get notice during test execution 3/ run phpunit tests (make sure auth_ldap tests are not skipped!) — These testing instructions assume that we already have a LDAP server setup with external users (at least one), and that we have correctly configured the LDAP authentication plugin to talk to the LDAP server. Set Authentication > LDAP > cron synchronization script > Removed ext user to "Suspend internal". Without applying the fix, run the auth/ldap/cli/sync_users.php script from the command line. Check that all the LDAP users are created/updated correctly in Moodle, and that all of them appear as 'enabled'. Remove an existing user in the LDAP server and re-run the sync.php script. Check that the Moodle internal user still appears as 'enabled' (but has 'nologin' as the authentication method). Check that the user can't login (even if it appears as 'enabled') Re-create the external user in the LDAP server and re-run the sync.php. Check that the Moodle internal user is 'revived', i.e., it appears as 'enabled' and has 'ldap' as the authentication method. Check that the user can login again and the user course data (grades, etc.) are still there. Remove the existing user in the LDAP server again. Now apply the fix and re-run the sync.php script. Check that the same Moodle internal user now appears as 'disabled' (aswell as having the 'nologin' authentication method). Check that the user can't login. Now re-create the external user in the LDAP server and re-run the sync script. Check that the Moodle internal user is 'revived', i.e., it appears as 'enabled' and has 'ldap' as the authentication method. Check that the user can login again and the user course data (grades, etc.) are still there.

      Authentication > LDAP > cron synchronization script > Removed ext user = "Suspend internal".

      Remove user from existing LDAP directory
      Running sync_users script manually appears to suspend user that was removed from LDAP directory
      User account does not appear suspended when viewed from within Moodle.

      Discussion here:

      https://moodle.org/mod/forum/discuss.php?d=230854

            skodak Petr Skoda
            flatlander Greg Padberg (Inactive)
            Iñaki Arenaza Iñaki Arenaza
            Damyon Wiese Damyon Wiese
            Rajesh Taneja Rajesh Taneja
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.