1

I'm trying to get my head round using DotNetOpenAuth and whilst I have had a certain amount of success following the source from the nerddiner project, I have hit some snags.

By the looks of things see here, though it appears that the version used in nerddinner (3.4.6.10357) nor the one on Nuget (3.4.7.11121) will not allow me to use Facebook or Twitters implementation. This is a bit of a killer blow for me using it.

I have found a sample using the OAuth 2.0 CTP here but that does not use the same ajax system as the nerddinner sample utilising the SelectorProviderButton.

Does anybody have an example of the two methods working together? I'm finding it very difficult to get any decent information.

Community
  • 1
  • 1
James South
  • 10,147
  • 4
  • 59
  • 115

1 Answers1

3

DotNetOpenAuth v3.4.x fully supports OAuth 1.0a, which is all that Twitter uses. So you should have no problem authenticating with Twitter.

Facebook uses OAuth 2.0, an older draft of the unfinalized spec, that is. So yes, you either code this up by hand in your app (which is actually quite easy) or you can use an (older) CTP of DotNetOpenAuth OAuth 2.0 preview. I say older because the newer builds of OAuth 2.0 preview implement a more recent draft than Facebook does, so it's incompatible.

I recommend given the crazily ill-state of affairs with OAuth 2.0, that you just follow Facebook's docs as an OAuth 2.0 client and code up the 2-3 URLs yourself for your app to log into Facebook for now.

BTW, there's no way currently to use SelectorProviderButton's with the OAuth protocol (1.0a or 2.0). It's strictly an OpenID feature.

Andrew Arnott
  • 80,040
  • 26
  • 132
  • 171
  • Thanks for that... I was really hoping that I would be able to mix the two but that was laziness as much as anything. Looks like I'll actually have to turn on my brain. – James South Sep 15 '11 at 09:28