Uploaded image for project: 'Moodle Community Sites'
  1. Moodle Community Sites
  2. MDLSITE-2662 First public runs of prechecker against various criteria
  3. MDLSITE-2690

Running the bulk checker leads to failed logins blocking the cibot account

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: Low Low
    • Integration
    • None

      It has been detected that the current "token login" used with all the Tracker jobs is leading (randomly) to the "cibot" account locked with a high (>=3) number of incorrect logins.

      Tracing down the problem, it seems to be happening always when the bulk prechecker is executed. Perhaps it's because of the duration of executions are > than the token TTL, or perhaps because some of the actions sometimes are using REST apis and the token only works for SOAP apis.

      https://bobswift.atlassian.net/wiki/display/JCLI/How+to+reduce+login+actions+for+multiple+requests

      In any case, it's clear that current "token login" is really unstable so this is about to move away from it and perform a login for every action, passing the server/login/pass always.

      First the bulk prechecker and then the other tracker jobs.

      Ciao

            stronk7 Eloy Lafuente (stronk7)
            stronk7 Eloy Lafuente (stronk7)
            Eloy Lafuente (stronk7) Eloy Lafuente (stronk7)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

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