WordPress OpenID plugin: Now providing

I was very pleased to find out today that the Word­Press OpenID plu­g­in was updat­ed. Among some gen­er­al fix­es, the newest ver­sion sup­ports act­ing as an OpenID provider. In oth­er words, I can use my “andrews​ki​.net” domain to sign in to any OpenID-enabled web­sites, of which there are plen­ty. I can then man­age my authen­ti­ca­tions with­in my Word­Press set­tings. All very good stuff.

(One heads-up: the OpenID plu­g­in encour­ages you to install the XRDS-Sim­ple plu­g­in. The descrip­tion is there, but I missed it.)

My gen­er­al goal is to make my domain as use­ful as pos­si­ble, and this is def­i­nite­ly a big step.

10 thoughts on “WordPress OpenID plugin: Now providing

  1. The OpenID plu­g­in works as a gen­er­al-pur­pose provider and man­ag­er, so you can not only sign in with your WordPress/OpenID but can also man­age your autho­riza­tions. Maybe you’ve been able to do that already, but the updat­ed plu­g­in is def­i­nite­ly major (it did not have that func­tion­al­i­ty before).

  2. I’ve dis­abled the plu­g­in for now until I can bet­ter test it. It seems to want to force OpenID ver­i­fi­ca­tion, when what I want is to allow it as a choice.

  3. @Dan: when del­e­gat­ing, the plu­g­in allows you to adver­tise any OpenID exten­sions sup­port­ed by your del­e­gate OpenID, such as SREG, Attribute Exchange, PAPE, etc. Sim­ply using the HTML meta tags does not allow for that. Addi­tion­al­ly, the plu­g­in lets you use Word­Press as your provider, with­out del­e­gat­ing any­where. While I would dis­cour­age that for most peo­ple, there are some who pre­fer it.

    @Andrew: what do you mean about the plu­g­in forc­ing OpenID ver­i­fi­ca­tion? There are cer­tain things you can force, such as using OpenID for new account reg­is­tra­tion, but those are all entire­ly option­al.

  4. @Will: Thanks for both of your infor­ma­tive com­ments. Per­haps I have it set up wrong (I tried to “unforce” every­thing), but when some­one who is not logged in tries to leave a com­ment, they are forced to go through OpenID ver­i­fi­ca­tion. (Though, now that I’m test­ing on my test domain, I can’t seem to repro­duce it any­more. Thoughts?

  5. I should also men­tion that I’m assum­ing any prob­lems with the com­ment form are a con­se­quence of my theme, but I just haven’t had the time to test any­thing yet.

  6. Com­menters are only prompt­ed to login via OpenID if the URL that they put in is a valid OpenID. If it’s not, then the com­ment is processed as usu­al. If you’d rather not over­load the web­site field in this man­ner, you can man­u­al­ly add a sep­a­rate OpenID input field to your com­ment form.

  7. Actu­al­ly, I would pre­fer to over­load my web­site field. :) So I’m assum­ing that the OpenID field is look­ing for a cer­tain com­ment div/ID and that my the­me’s field isn’t iden­ti­fied cor­rect­ly? (I checked, and it does work on Kubrick.)

Leave a Reply

Your email address will not be published. Required fields are marked *