Posted 3 years ago #
I have installed the plugin on my blog, and added the field to the comments form, as well as disabling the ajax that interfered with OpenID previously.
Now, when i enter any openID data (not https openID, i havn't fixed that yet, just a claim.id), it accepts it, but claims it needs the Name and email. Try for yourself.
Doesn't having to input the name and email defeat the purpose of OpenID?
Posted 3 years ago #
See the second paragraph of my reply here to understand what's going on. This is a change in the behavior from 2.x, and I should have documented that better... sorry about that. I've added an option that will be in the 3.1 release that allows you to bypass the username and email check for OpenID comments. Enabling this option makes it behave the same way it did in pre-3.0 releases.
Posted 3 years ago #
Ah, thank you. It seemed to be the OpenID provider i was using didn't provide these details, as MyOpenId worked fine.
If possible, could you make it so OpenID url links for names goes to the Homepage as specified through the OpenID, instead of to the OpenID?
I know many services let you set your own personal url.
As for the libcurl update, any way to preform that on a shared host? I use Chi.mp, as do a lot of my co-writers, and it is secure.
Posted 3 years ago #
If an individual wants the link to be their homepage, then they would need to setup their homepage as an OpenID and delegate to their OpenID provider. The idea is that OpenID comments are visually denoted with the OpenID logo, so that you know the commenter was authenticated using the displayed OpenID URL. If you change that URL to something that wasn't actually authenticated, it defeats the purpose.
What libcurl update are you referring to? The thing with the out of date certificates? I know some of the guys at chi.mp, so I can contact them if I know what the problem is.
This topic has been closed to new replies.
