Inconsistent response between Development environment and Production

Yahoo recently stopped working on a website I maintain.  I upgraded to a later version of DotNetOpenAuth (3.4.7) which works in our QA and  Development environment, but doesn't work in production.  Configuration and binaries are identical - and I've reviewed the responses (in Fiddler) and with the exception of the openid.assoc_handle, openid.return_to and openid.realm which must be different - it's identical.  However - in production, I'm getting "Sorry! There is an error with the request we received from the website you are trying to use. Please try again in a few minutes. If this error persists please contact the site administrator.".  

Is there any chance that there's something on the Yahoo side that's marking the realm or site as bad?  

Our registration page can be found here: https://account.cancer.org/profile/register.aspx?realm=https%3A%2F%2Fwww.cancer.org%2F&returnUrl=http%3A%2F%2Fwww.cancer.org%2F

1 Reply
  • Looks like it's being blocked.  I manually requested an assoc_handle and generated a request URL.  When I use the URL for our dev site, the request goes through, when I use the URL for the prod site - I get the error that it's invalid.  The only difference between the two? realm and return_to.  Did we end up on some sort of blacklist or something?

Recent Posts

in OpenID General Discussion