You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 7, 2024. It is now read-only.
I get an OpenID Authentication Error while leaving a comment.
What steps will reproduce the problem?
1. Filling the Openid field (or all the fields of the comment form)
2. Pressing the submit comment button.
3. Gettig the Livejournal openid authentification screen and accepting the
request (tried both for one time and forever).
4. retrned to blog with an error:
OpenID Authentication Error
We were unable to authenticate your claimed OpenID, however you can
continue to post your comment without OpenID:
5. Able to post a comment without an OpenID
What is the expected output? What do you see instead?
Expect to post comment with an OpenID.
Instead get an OpenID Authentication Error
We were unable to authenticate your claimed OpenID, however you can
continue to post your comment without OpenID:
What version of the product are you using? On what operating system?
WP 2.8.2 , openid 3.2.3, Mandigo theme
FF 3.5.1
Windows XP
Please provide any additional information below.
Did not modify OpenID plugin or WP, except added a line of code to show the
OpenID field, as suggested:
<p><input type="text" name="openid_identifier" id="openid_identifier" />
<label for="openid_identifier"><small>OpenID URL (for example:
mactep.livejournal.com)</small></label></p>
Original issue reported on code.google.com by netocrat...@gmail.com on 30 Jul 2009 at 8:07
The text was updated successfully, but these errors were encountered:
Any news on this one? I recently have this same problem. However the strange
thing is
I've tried on 2 different servers with almost similar specs (according to the
host
provider) and it works on the first, the other fails in the way described above.
Original comment by sjoerdlo...@gmail.com on 24 Oct 2009 at 9:08
for me I've found the decision, it was a problem from a host's side - caused by
the
Apache module mod_security. I asked provider to disable some rules to my domain
and all
is ok now.
Original comment by liquidbl...@gmail.com on 12 Jan 2010 at 4:05
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Original issue reported on code.google.com by
netocrat...@gmail.com
on 30 Jul 2009 at 8:07The text was updated successfully, but these errors were encountered: