"Authenticate filter not called" (but able to login from other computer?)

Hey mate,
Sh-t, yeah, sorry, I forgot to reply to that one.

Yeah, I tried IE10 and Chrome.

And yeah, apologies, when I said caching, I meant I had cleared it all. It was about 2am here when I wrote that. Was very tired. Still am.

Cheers
Glen

Glen:

Did the problem _arise_ when you switched between browsers?

Can you please try to uncomment the log() calls and reproduce the problem?

Thanks,

–Dan

Daniel,

Thanks for helping us look into this. I’ve now had multiple users report this on two separate WPMU instances, neither of which are running any other plugins which call the authenticate() function. I’ve updated your plugin to the latest version and uncommented out all of the logging calls. I’ll wait for this error to reproduce itself and then share the sanitized log data so we can figure out what’s going on.

Same problem here. Multisite and unable to login with network admin.

Hi Lponce:

Can you please provide valuable assistance by doing the debugging / testing I’ve mentioned in various posts? Another “me too” post doesn’t move the ball forward.

Thanks,

–Dan

Sorry but I don’t have time for test and debug. I found another plugin which doesn’t break my sites. Wish you the best for your plugin.

I had the same problem when I updated from .39 to .40 – every page seemed to be redirecting to login.php and immediately show that error.

I renamed the plugin folder to deactivate it, then implemented your logging, but when i reactivated the plugin I did not get the errors again.

Nothing else changed during that time.

I’ve got the same issue. I’ve recently upgraded from 0.39 to 0.40.

Disabling the plugin gets me back into the wordpress site.
Reinstalling immediately gives the error “Authenticate filter not called”.
I’ve tried with Safari and Chrome.

I can’t find the log() function to enable it ?? Is this function still there?

Thanks!

Ok so I was able to grab some log data after replicating the issue (actual paths and usernames redacted):

2013-06-24 23:10:07 auth_cookie_expired: some_user
2013-06-24 23:10:07 auth_cookie_expired: some_user
2013-06-24 23:10:07 auth_cookie_expired: some_user
2013-06-24 23:10:07 authenticate: empty user_name
2013-06-24 23:10:07 wp_login_failed: authenticate filter not called
2013-06-24 23:10:07 wp_login_failed: authenticate filters
2013-06-24 23:10:07 wp_login_failed: backtrace: [{"function":"wp_login_failed","class":"login_security_solution","object":{"dir_dictionaries":"\/home\/vhosts\/webroot\/wp-content\/plugins\/login-security-solution\/pw_dictionaries\/"},"type":"->","args":[""]},{"file":"\/home\/vhosts\/webroot\/wp-includes\/plugin.php","line":406,"function":"call_user_func_array","args":[[{"dir_dictionaries":"\/home\/vhosts\/webroot\/wp-content\/plugins\/login-security-solution\/pw_dictionaries\/"},"wp_login_failed"],[""]]},{"file":"\/home\/vhosts\/webroot\/wp-includes\/pluggable.php","line":485,"function":"do_action","args":["wp_login_failed",""]},{"file":"\/home\/vhosts\/webroot\/wp-includes\/user.php","line":53,"function":"wp_authenticate","args":[null,null]},{"file":"\/home\/vhosts\/webroot\/wp-login.php","line":608,"function":"wp_signon","args":["",""]}]

The exact error as shown on the page:

Login Security Solution: authenticate filter not called

So clearly the plugin is expiring the auth cookie as it should, and then WordPress seems to be trying to reauth with an empty username field?

Gplasky:

Thank you, thank you, thank you! That debugging information led me to the solution fairly quickly.

This issue has been fixed in the 0.41.0 release.

–Dan

Thanks – update solved the issue. Could there be a button to enable debug/logging in the settings? That way you would get feedback quicker ??