Download
2012-03-11, 02:20:38
Ok, well since we have 2 issues being reported here, can we maybe clarify or start a new thread on the logins failing issue.
This thread is about failed logins log file.
The failed logins log is only created and written to, when a login attempt is made for an existing user and the password is wrong. If you enter a random username it WILL NOT LOG the failure.
The file is not written to or created when a user doesn't exist. This is how it is coded in 3.1 by design.
And I believe it is very confusing and should be changed. But maybe some protection or log rotation will need to be added to prevent the log from becoming to large.
Regarding people with login issues. How does it fail ?
Do you get a redirect back to the login form, whats the url afterwards?
Do you get an error ? A blank page.
The only time iIhave seen this issue, is with a corrupt cookie that redirects over and over back to login page, this is called a login loop. Deleting the cookie fixes it. Although I haven't been able to reproduce it to find out the actual cause.
This thread is about failed logins log file.
The failed logins log is only created and written to, when a login attempt is made for an existing user and the password is wrong. If you enter a random username it WILL NOT LOG the failure.
The file is not written to or created when a user doesn't exist. This is how it is coded in 3.1 by design.
And I believe it is very confusing and should be changed. But maybe some protection or log rotation will need to be added to prevent the log from becoming to large.
Regarding people with login issues. How does it fail ?
Do you get a redirect back to the login form, whats the url afterwards?
Do you get an error ? A blank page.
The only time iIhave seen this issue, is with a corrupt cookie that redirects over and over back to login page, this is called a login loop. Deleting the cookie fixes it. Although I haven't been able to reproduce it to find out the actual cause.
