views:

241

answers:

4

Hi, I am trying to use the CTP to connect with Facebook over OAuth 2.0.

I can get the initial request to Facebook working OK, but when it comes back and we call:

client.ProcessUserAuthorization(null); // Where null will become an HttpRequestInfo object

I get a 400 BAD REQUEST error.

I haven't really done much with the initial codebase; merely set the optional values to null (we're still on .NET 3.5). Any clues would be much appreciated.

Also, and i guess this is more of a question to Andrew specifically; is there a forum / blog for any of this stuff, or anywhere that will give regular updates? It would be great to know a few things:

i) Planned release date of the DotNetOpenAuth with OAuth 2.0 ii) Whether .NET 4.0 will be a pre-requisite

Anyway, any suggestions would be most welcome.

Thanks,

Pete.

A: 

I have this problem too.

Please help.

smith
+1  A: 

I'm also seeing this problem. It was working a few weeks ago. Someone else seems to have reported this @ http://forum.developers.facebook.net/viewtopic.php?id=74021.

olivehour
I ended up just writing my own facebook client class. It's not hard to create a web request to facebook connect, get back the code, and then use it to claim a token. For some reason, the DNOA code is failing on the last step, sending the code to get an access token. If you create your own web request for the second part, you can sidestep the error.
olivehour
A: 

I have this problem too.

Please help.

Miekje