OpenID in WordPress no longer works.

• 

  simonodoherty · Member · Mar 19, 2015 at 3:26 pm

  • Copy link
  • Add topic to favorites

  I am trying to log into StackOverflow with my OpenID. It worked before, but now I get “Redirects on POST requests that are to untrusted servers is not supported.” and login is denied. Checking meta for StackExchange they mention the issue is at the WordPress end.

  The blog I need help with is: (visible only to logged in users)

• 

  thatrobyn · Member · Mar 19, 2015 at 6:20 pm

  • Copy link

  Hey there!

  Please log out of WordPress.com, or any other sites that you’ve logged into using your OpenID.

  Then, go through the login process at StackOverflow using these instructions:
  https://en.support.wordpress.com/settings/openid/

  Then, please get back to me and let me know the results.

  Also, can you tell me what happens when you attempt to log into any other OpenID-login-accepted sites with your WordPress.com ID/password?

  Thanks much!

• 

  simonodoherty · Member · Mar 20, 2015 at 2:30 pm

  • Copy link

  I did all that and didn’t help. It appears this has been ongoing for a while.

  http://meta.stackoverflow.com/questions/284331/redirects-on-post-requests-that-are-to-untrusted-servers-is-not-supported

  http://meta.stackexchange.com/questions/245329/wordpress-openid-redirects-on-post-requests-that-are-to-untrusted-servers-is-no

  I tried a different OpenID site (live journal. I don’t have an account with them). WordPress picked up they wanted access and added them to trusted sites. However when I go to log in I get this error:

  naive_verify_failed_network: Could not contact provider to verify signature

  I tried StackExchange (only other openID I know of, tried a few from your link). I get this.

  Unable to log in with your OpenID provider:

  Redirects on POST requests that are to untrusted servers is not supported.

  I’ve also tried this on different machines (some I had not logged into before).

• 

  thatrobyn · Member · Mar 20, 2015 at 6:58 pm

  • Copy link

  Hi there!

  Thank you so much for this additional information. The details are helpful.

  I’ve notified our staff of this issue. One of us will be in touch as soon as there is a resolution.

  Thanks for your patience with this.

• 

  simonodoherty · Member · Apr 28, 2015 at 3:10 pm

  • Copy link

  So what is happening with this? OpenID is still not being accepted.

• 

  thatrobyn · Member · Apr 29, 2015 at 5:17 pm

  • Copy link

  Hey there,

  This is still an issue that’s in our queue, but in the meantime, one of my colleagues found a workaround for you.

  The conflict appears to be isolated to users with a WordPress.com custom domain, who utilize OpenID to log into StackExchange.com.

  Here’s your way in:

  • You can temporarily change your primary domain on your WordPress.com site to the .wordpress.com address on your My Domains page (found HERE).
  • Once you’ve done that, you can log into stackexchange.com with your WordPress.com URL.
  • Then, you can adjust your primary domain back at WordPress.com at anytime.

  I know this isn’t the most convenient fix, but if you have no other way to log into StackOverflow, it will allow you access.

  Let’s stay in touch and I’ll let you know when a resolution is reached. Thanks much.

• 

  simonodoherty · Member · May 6, 2015 at 12:11 pm

  • Copy link

  Only got to check this now. That doesn’t work.

  If I change the primary domain, then StackExchange thinks I am a new user.

• 

  thatrobyn · Member · May 6, 2015 at 7:56 pm

  • Copy link

  Hey there!

  A few things I’d like to check on:

  What URL did you enter in the OpenID field at https://stackoverflow.com/users/login-add in your last test?

  When you switch to the sodohertydotcom.wordpress.com domain at https://sodohertydotcom.wordpress.com/wp-admin/paid-upgrades.php?page=domains you should try both domains at StackExchange WHILE the primary domain is set to sodohertydotcom.wordpress.com on the WordPress.com side. Is this the method you used?

  Do you recall what the exact URL was that you used originally? It’s possible that if it was the custom domain and not sodohertydotcom.wordpress.com, then the workaround may not work for you. If that’s the case, then it’s possible we will need to wait for an update from our developers which may take some time as this issue affects very few people.

  Thanks again!