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

Deprecate cas and ldap CLIs

XMLWordPrintable

    • MOODLE_30_STABLE
    • MOODLE_30_STABLE
    • MDL-51824-master
    • Hide
      LDAP user sync
      1. Enable and setup LDAP authentication method.
      2. Run the sync_users CLI script: 

        php auth/ldap/cli/sync_users.php

      3. Make sure you see the following message: 

        [AUTH LDAP] The users sync cron has been deprecated. Please use the scheduled task instead.

      4. Make sure the user synchronization is working as expected.
      5. Go to Site administration ► Server ► Scheduled tasks and enable LDAP users sync job, setting all fields to *.
      6. Run the same CLI script above and make sure you see the message: 

        [AUTH LDAP] The scheduled task sync_task is enabled, the cron execution has been aborted.

      7. Make sure the execution was aborted and the synchronization didn't happened.
      CAS user sync
      1. Enable and setup CAS server WITH LDAP method.
      2. Run the sync_users CLI script: 

        php auth/ldap/cli/sync_users.php

      3. Make sure you see the following message: 

        [AUTH CAS] The sync users cron has been deprecated. Please use the scheduled task instead.

      4. Make sure the user synchronization is working as expected.
      5. Go to Site administration ► Server ► Scheduled tasks and enable LDAP users sync job, setting all fields to *.
      6. Run the same CLI script above and make sure you see the message: 

        [AUTH CAS] The scheduled task sync_task is enabled, the cron execution has been aborted.

      7. Make sure the execution was aborted and the synchronization didn't happened.
      Show
      LDAP user sync Enable and setup LDAP authentication method. Run the sync_users CLI script: php auth/ldap/cli/sync_users.php Make sure you see the following message: [AUTH LDAP] The users sync cron has been deprecated. Please use the scheduled task instead. Make sure the user synchronization is working as expected. Go to Site administration ► Server ► Scheduled tasks and enable LDAP users sync job , setting all fields to *. Run the same CLI script above and make sure you see the message: [AUTH LDAP] The scheduled task sync_task is enabled, the cron execution has been aborted. Make sure the execution was aborted and the synchronization didn't happened. CAS user sync Enable and setup CAS server WITH LDAP method. Run the sync_users CLI script: php auth/ldap/cli/sync_users.php Make sure you see the following message: [AUTH CAS] The sync users cron has been deprecated. Please use the scheduled task instead. Make sure the user synchronization is working as expected. Go to Site administration ► Server ► Scheduled tasks and enable LDAP users sync job , setting all fields to *. Run the same CLI script above and make sure you see the message: [AUTH CAS] The scheduled task sync_task is enabled, the cron execution has been aborted. Make sure the execution was aborted and the synchronization didn't happened.

      With MDL-46623, the old cas and ldap syncs can be run from the new scheduled-tasks system.

      In order to keep things working for existing sites it was agreed to:

      1) DONE: keep the new scheduled tasks disabled by default.
      2) add a deprecated warning to CLIs, stating that they will be erased for X.Y and people should be moving to the scheduled tasks before that release.
      3) prevent the CLIs to run if the new (replacing) scheduled task has been enabled (to avoid concurrency).
      4) Document this 1-2-3 everywhere in auth/scheduled tasks docs.

      Ciao

            lameze Simey Lameze
            stronk7 Eloy Lafuente (stronk7)
            Adrian Greeve Adrian Greeve
            Andrew Lyons Andrew Lyons
            Rajesh Taneja Rajesh Taneja
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved:

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