Authentication

Hello Zachary,

While the message is cryptic, reason with "id = 3" just means that someone tried to log in with a valid username but with a wrong password. "id = 1" would mean that someone tried to log in with an invalid username.

Hi Zachary,

Thanks for posting this login failure. At our site,id'3' is an admin account. Several students reported a login failure. When I go to Site administration -> Reports -> Logs, this is what I see:

a) After the user viewed a message from id'3', the login fails many times, but not always.

b) The log file reports "cli" as origin, not the web. (I don't know what cli stands for)

c) The reason for the login failure is always id'3', not any other id.

Here are the screenshots:

Below is another user, also with a login failure:

Now the next one (Mayson) doesn't fit the pattern. He has not viewed a message with id'3' nor did he switch from "cli" to "web" in the right column.

And here is another one where I cannot see a pattern.

Does anybody know why an admin account can cause so many login failures? Most of the computer are in our library, but not all.

With kind regards,

Hartmut

/** Login attempt successful. */
define('AUTH_LOGIN_OK', 0);
/** Can not login because user does not exist. */
define('AUTH_LOGIN_NOUSER', 1);
/** Can not login because user is suspended. */
define('AUTH_LOGIN_SUSPENDED', 2);
/** Can not login, most probably password did not match. */
define('AUTH_LOGIN_FAILED', 3);
/** Can not login because user is locked out. */
define('AUTH_LOGIN_LOCKOUT', 4);
/** Can not login becauser user is not authorised. */
define('AUTH_LOGIN_UNAUTHORISED', 5);