Comments on: Minor Plugin Updates

By: Ben Chun

Ben Chun — Wed, 02 Apr 2008 01:11:04 +0000

I left a comment on an older post before I found this — sorry!

As for wp_authenticate being deprecated: I looked in wp-includes/pluggable.php and wp_authenticate is there. It does say @since 2.5 which seems a little strange. Perhaps it implemented differently prior to 2.5?

Anyway, the workaround from Ryan P shows us that wp_authenticate is still being called on regular page loads. But it looks like wp-login.php no longer directly calls do_action_ref_array(’wp_authenticate’, array(&$user_login, &$user_pass)); but instead calls wp_signon() which is in wp-includes/user.php

I think this change in wp-login.php is the culprit, because wp_signon() wants to either be passed some credentials or have them posted from a form — and it will return before calling wp_authenticate if that’s not the case. In prior versions, the do_action_ref_array(’wp_authenticate’, array(&$user_login, &$user_pass)); happened even if the user_login and user_pass were empty.

What’s maddening is that I don’t know where to find the WordPress documentation for this change. Obviously someone had an idea of how they want authentication to work in WordPress 2.5. How can we know what they were thinking? It doesn’t seem that wp_signon is pluggable, so how is this stuff supposed to work?

By: Ryan P

Ryan P — Tue, 01 Apr 2008 13:48:17 +0000

Ok, thank you.
This guy says wp_authenticate is deprecated in 2.5: http://adambrown.info/p/wp_hooks/hook/wp_authenticate
so I’m not sure what the replacement would be.

By: dwc

dwc — Tue, 01 Apr 2008 12:05:16 +0000

Ryan P,

I briefly tested 2.5 last week and ran into the same behavior. I haven’t had a chance to dig into the problem more, but I hope to do so this week.

By: Ryan P

Ryan P — Mon, 31 Mar 2008 23:09:32 +0000

I was using your HTTP Authentication plugin for 2.3.3 just fine.
I upgraded to 2.5 today, and now whenever I login with my custom process, I get taken to wp-login.php.
From there, I can enter in anything in the username and password fields and hit submit.
After it re-displays the login saying incorrect password, I type in /wp-admin in my location bar manually, and it lets me into the admin area.
But, I HAVE to type in something to the username/password fields first.

It’s almost like add_action(’wp_authenticate’…) is not being called anymore in 2.5.

Any thoughts on why it’s not working?

Thanks!

By: DeezJee

DeezJee — Thu, 06 Mar 2008 20:40:01 +0000

That’s it! Thank you very much!
Keep up the good work

By: dwc

dwc — Wed, 05 Mar 2008 22:21:22 +0000

DeezJee,

Try this recommendation - the URL is a little different.

By: DeezJee

DeezJee — Wed, 05 Mar 2008 22:17:50 +0000

You’ve got a nice plugin! But I can’t get it to work with iCal from my online .mac account
When I use the url to the ics from the txt file, I get everything to work. So I assume it has got something to do with the ics from my online calendar (http://ical.mac.com/deezjee/tourlist)
Can you help me?

By: dwc

dwc — Fri, 25 Jan 2008 00:26:50 +0000

Ryan,

What version of WordPress are you using?

I’m not familiar with mod_ntlm but for some reason it sounds like it’s not protecting the directory. Do your server access logs show a username?

By: Ryan

Ryan — Thu, 24 Jan 2008 01:54:44 +0000

Thanks for your plugin. Im using it with mod_ntlm and apache for an intergrated SSO. I am having a problem where unless I proctect the entire Wordpress directory with NTLM, it will fail to authenticate and bring up the “No REMOTE_USER found……”. I have applied NTLM to be used for /wp-login.php and /wp-admin/. Are there any files I’m missing?

Thanks in advance

Ryan

By: Joe

Joe — Sun, 06 Jan 2008 01:36:14 +0000

I had a calender with my primary e-mail/google calendar as a test, and it worked.

Now i’ve switched to the calendar I WANTED it to work with (i.e. different e-mail) and it is telling me there is a parsing error.

If I switch the e-mail back to the original one, it works. Any idea what’s up?