I was very pleased to find out today that the WordPress OpenID plugin was updated. Among some general fixes, the newest version supports acting as an OpenID provider. In other words, I can use my “andrewski.net” domain to sign in to any OpenID-enabled websites, of which there are plenty. I can then manage my authentications within my WordPress settings. All very good stuff.
(One heads-up: the OpenID plugin encourages you to install the XRDS-Simple plugin. The description is there, but I missed it.)
My general goal is to make my domain as useful as possible, and this is definitely a big step.
10 Comments
Ya know, i do that already… required two lines of code… is it different than the openid code?
The OpenID plugin works as a general-purpose provider and manager, so you can not only sign in with your WordPress/OpenID but can also manage your authorizations. Maybe you’ve been able to do that already, but the updated plugin is definitely major (it did not have that functionality before).
I’ve disabled the plugin for now until I can better test it. It seems to want to force OpenID verification, when what I want is to allow it as a choice.
@Dan: when delegating, the plugin allows you to advertise any OpenID extensions supported by your delegate OpenID, such as SREG, Attribute Exchange, PAPE, etc. Simply using the HTML meta tags does not allow for that. Additionally, the plugin lets you use WordPress as your provider, without delegating anywhere. While I would discourage that for most people, there are some who prefer it.
@Andrew: what do you mean about the plugin forcing OpenID verification? There are certain things you can force, such as using OpenID for new account registration, but those are all entirely optional.
@Will: Thanks for both of your informative comments. Perhaps I have it set up wrong (I tried to “unforce” everything), but when someone who is not logged in tries to leave a comment, they are forced to go through OpenID verification. (Though, now that I’m testing on my test domain, I can’t seem to reproduce it anymore. Thoughts?
I should also mention that I’m assuming any problems with the comment form are a consequence of my theme, but I just haven’t had the time to test anything yet.
Commenters are only prompted to login via OpenID if the URL that they put in is a valid OpenID. If it’s not, then the comment is processed as usual. If you’d rather not overload the website field in this manner, you can manually add a separate OpenID input field to your comment form.
Actually, I would prefer to overload my website field.
So I’m assuming that the OpenID field is looking for a certain comment div/ID and that my theme’s field isn’t identified correctly? (I checked, and it does work on Kubrick.)
check to make sure your theme is calling wp_footer()
My footer.php contains “< ?php do_action(‘wp_footer’, ”); ?>”; is that what I should hope to see?
Where’s the best place to get support for this?