wp-openid 2.0 released

I’m sure people are tired of me talking about how soon this will be released, so I promise I’ll shut up now. I’ve just tagged version 2.0 of wp-openid, a WordPress plugin which allows you to use OpenID for authenticating users and commenters. There are a number of really cool features we just weren’t able to get into this release, so that just means more to come in the next version. Go download it and have fun. Release notes, screenshots, FAQ, install instructions, etc can all be found there. I’ll probably be unplugged most of the weekend, so try not to break anything too bad. ;)

Comments

  1. Hello!
    I’ve installed your OpenID Plugin on my website but still couldn’t make it work. Can you explain what I need to fill out if I have an account on the Livejournal website, as example?

  2. Hi, I’ve successfully implemented your plugin on my blog, http://www.geekie.org , but I’ve found that it’s not possible for an administrator to edit a user’s identity URL’s. Perhaps this would make for a useful feature?

    Fortunately, the OpenID login and profile implementations work great! No bugs, as far as I can tell. Of course, I’ve made some changes to the source code in order to integrate it with my blog’s design.

    Thanks for the great work.

  3. @Anton (Anonymous): I’d need a bit more information to know what’s wrong. Feel free to contact me off-site or in the WP support forums.

    @Frederick: perhaps I’m not understanding the use case, but why should an administrator be able to edit a user’s Identity URLs? That would require that either A) the admin knows the password for the user’s OpenID account, which is not likely or B) we don’t actually verify ownership of the OpenID, which completely defeats the purpose.

  4. Congratulations on an excellent and much-needed plugin!

    I’m having trouble with delegated OpenID.

    I’m http://robertjones.myopenid.com and have delegated http://www.jonesieboy.co.uk/blog to refer to that openid

    When I try to post a comment using the original myopenid url, all is well, but when I use my blog url, my blog (and yours) chuck back a “need name and email” error, despite the fact that the openid checker reports that my blog is a functioning openid.

    Any ideas?

  5. I love the idea of this plugin but it simply returns a fatal error when I try and activate it….
    “Plugin could not be activated because it triggered a fatal error.”

    I cant see where to debug it at all can you give me any advice ?
    (logs etc )

  6. Nice to see that here the 2.0 specific directed identity feature worked like a charm. I entered openid.ee as the website URL and the comment got a really obvious Anonymous name even.

    Unfortunately on my site it doesn’t work that smoothly. I probably should work with templates a bit. Also Spam Karma did not like the post with the anonymous URL.

    Other than that – great plugin, shall use it, thanks!

  7. I’m having an issue that I didn’t have before.

    I’m running my own OpenID server, using Siege’s phpMyID, and I can log in using http://williamgunn.org/me/OpenID.config.php?openid.mode=login, (delegated as http://williamgunn.org), but if I use that as anywhere(own my site, or here, or a couple other sites I tried, I get “We were unable to authenticate your OpenID.”

    It used to work, and now without changing any of the phpMyID code, it’s not working anymore, anywhere.

    Any insight?

  8. I’m encountering an error with this plugin:

    Error: OpenID assertion failed: Bad signature

    Any thoughts about how to associate my OpenID with my WordPress account?

  9. I’ve figured out that I likely don’t have gmp, so I’m looking at adding this to the plugin somewhere:

    define(’Auth_OpenID_NO_MATH_SUPPORT’, true);

    but where?

  10. Wow. Here it worked. Strangely I get “Bad signature” on my own WordPress site trying to use the IdS on the same machine (MyOpenId does work though). I’ll have to dig deeper into that…

  11. hey ! i installed openid but unable to get it on to my comments and login page ,how can i manually edit the comments page,the readme isnt helpful

  12. Turns out that the problem described above was a bug in the JanRain PHP libs (but I don’t know on which side of the protocol) that garbled the shared secret. After deleting the association from both databases it worked.

  13. Well, de-activating, re-activating (2 times) the plug-in on my website made it work finally. Certainly related to what Thomas mentions.

    Do you plan to re-add the FOAF/SIOC features in the future ? I’ll post a simmple hack for this on my blog for this release soon.

  14. @Alexandre: yes, there is an open ticket for adding FOAF, among other protocols. I can’t guarantee when I’ll get it added, there are method stubs in the plugin where this planned to go and patches are always welcome. I spent too much time on wp-openid to get 2.0 released, so now I’m spending a little time on other projects (and my day-job) :).

  15. It’d be a useful plugin, if the readme.txt included some clues on how to tweak my comments.php so the plugin can work. I’ve activated the plugin but I’m completely lost.

  16. David Collantes

    Having the same problem as John Jones. The plugin will refuse activation with a:

    “Plugin could not be activated because it triggered a fatal error.”

    Where are the errors logged, so I can start troubleshooting?

  17. David Collantes

    [quote comment="15414"]

    I love the idea of this plugin but it simply returns a fatal error when I try and activate it….
    “Plugin could not be activated because it triggered a fatal error.”

    I cant see where to debug it at all can you give me any advice ?
    (logs etc )

    [/quote]

    I should have used the quote option to refer to the user that is having a similar problem to me. Again, getting the same message while trying to activate, and it will not load.

  18. … and this is the second half of the test in order to agree with Rodolfo Zanzibar: what’s the point on having OpenId if it doesn’t show your identity but merely your link? How can I modify my template in order to show it? (I am using now the core WP comment_author_link function)

    (Check it in Blogger, this issue is solved there!!)

  19. Question, how can I make the Website field only look for an open ID if the website is an openID provider (like you have done in your comment field)? If change the input name of the website field, then it always looks for authentication.

  20. @Divided By Zero: this should be the default behavior of the plugin… you shouldn’t need to manually change your template at all, that is handled by some jQuery code on the client side. It does require that you NOT select “Users must be registered and logged in to comment”, which is pretty typical.

  21. Thanks for the answer Will, but unfortunately it does not work for me. The plugin mentions that it works with Kubrick or Sandbox themes but mine is based on Hemingway :-/

    Generally when I added the plugin, nothing seemed to happen to the template. When I changed the name of the website field to “openid_url” then it always asks for authentication and fails if it is missing. If I keep the field as “url” then it never asks for authentication.

    I’ve made a thread of the WP forums if that is easier for you

  22. Hey there, I’m using a version of Wordpress running on localization and the most recent Wordpress, and I’m having trouble adding an OpenID to my account. Creating an account with an OpenID is no problem, but retroactively adding an OpenID does not work; after requesting the authorization from the server, and getting redirected back, I end up on the users admin page with the ID not being added to the account. Is there a common reason for this, or do I need to pester admins for logfiles?

Trackbacks

  1. [...] security on anything that I sign into with OpenID. I’m using it for this site with openID+ v2.0(released friday), although the previous versions have been [...]