Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-14584 META: NTLM problems
  3. MDL-14078

NTLM authentication incorrectly reports automated login failure when login is successful

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.9
    • Fix Version/s: 1.9.5, 2.0
    • Component/s: Authentication
    • Labels:
      None
    • Environment:
      windows 2000, Apache 2.2.8, Postgresql 8.3.1, PHP 5.2.5, Moodle 1.9 latest
    • Affected Branches:
      MOODLE_19_STABLE
    • Fixed Branches:
      MOODLE_19_STABLE, MOODLE_20_STABLE

      Description

      The automated login routine starts, after a few seconds (less than 10) the automated login failed message is displayed, then the user is presented with the login screen, meanwhile the login was actually successful and at the top left of the login screen the message "You are logged in as Username (logout)" is displayed.

      I have extended the time out figure from 3 to 30 seconds and still get this result on many occasions (a few successfully identify the login succeeded), yet clearly the login process is completing successfully in much less time than this.

      When NTLM authentication was not part of the core it always identified correctly whether the login had succeeded or not.

      Now the situation is very confusing for users, who are consistently successfully logging in automatically whilst being told their login has failed!

      Is it not possible to correct the testing used so that successful logins are correctly identified?

      Kind regards

      Johnathan Kemp

        Attachments

          Activity

            People

            Assignee:
            iarenaza Iñaki Arenaza
            Reporter:
            johnathankemp Johnathan Kemp
            Participants:
            Component watchers:
            Adrian Greeve, Jake Dallimore, Mathew May, Mihail Geshoski, Peter Dias
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Fix Release Date:
              13/May/09