Suddenly DotNetOpenAuth returns (400) Bad Request

Question

My application has been deployed for almost 6 months, and the latest version was about 3 weeks ago.

Suddenly, Facebook Auth stopped working today. Webapp was not changed or redistributed, and the settings of the facebook application were not changed.

Twitter authentication still works correctly.

This is an exception:

DotNetOpenAuth.Messaging.ProtocolException: Error occurred while sending a direct message or getting the response. ---> System.Net.WebException: The remote server returned an error: (400) Bad Request. at System.Net.HttpWebRequest.GetResponse() at DotNetOpenAuth.Messaging.StandardWebRequestHandler.GetResponse(HttpWebRequest request, DirectWebRequestOptions options) --- End of inner exception stack trace --- at DotNetOpenAuth.Messaging.StandardWebRequestHandler.GetResponse(HttpWebRequest request, DirectWebRequestOptions options) at DotNetOpenAuth.Messaging.StandardWebRequestHandler.GetResponse(HttpWebRequest request) at DotNetOpenAuth.Messaging.Channel.GetDirectResponse(HttpWebRequest webRequest) at DotNetOpenAuth.Messaging.Channel.RequestCore(IDirectedProtocolMessage request) at DotNetOpenAuth.Messaging.Channel.Request(IDirectedProtocolMessage requestMessage) at DotNetOpenAuth.OAuth2.ClientBase.UpdateAuthorizationWithResponse(IAuthorizationState authorizationState, EndUserAuthorizationSuccessAuthCodeResponse authorizationSuccess) at DotNetOpenAuth.OAuth2.WebServerClient.ProcessUserAuthorization(HttpRequestInfo request) 

Any idea what could happen? I don’t see anything on Facebook about violation of changes or deterioration of the service at the moment.

Answer 1

He started working again, making me believe that it was a mistake at the end of Facebook.

Answer 2

Most likely, Facebook has finally updated its OAuth 2.0 support to meet the later draft OAuth 2.0 specification, which is not compatible with the version of DotNetOpenAuth used. Try downloading the latest CTP DotNetOpenAuth and see if it helps.

However, there has never been a guarantee of compatibility with the likes of Facebook or another OAuth 2.0 server. OAuth 2.0 is not the final specification, and such compatibility issues are almost guaranteed.