0

I've seen this Two legged OAuth using DotNetOpenAuth but it doesn't provide any details on how to remove one of the legs.

I am finding the code quite hard get my head around (using DotNetOpenAuth 4.0). Can anyone give me any pointers on how to modify the samples to do a two-legged auth?

Community
  • 1
  • 1
Ian1971
  • 3,666
  • 7
  • 33
  • 61

2 Answers2

3

From the service provider, it is a simple matter of authorizing the request token immediately before before returning what normally is an unauthorized request token. Since the service provider already has to provide code to generate and store request tokens, this should be straightforward.

From the consumer, it's simply that you skip the redirect step. There's a sample of this in the OAuthConsumer samples' GoogleApps2Legged.aspx code-behind.

Andrew Arnott
  • 80,040
  • 26
  • 132
  • 171
  • Is this the same for OAuth 2? The GoogleApps2Legged example seems to be OAuth 1 – Ian1971 Apr 04 '12 at 11:26
  • You are correct. Google Apps is an OAuth 1.0 service. OAuth 2 doesn't use "2-legged oauth" in the 1.0 sense. Instead, it has a "client credentials grant". – Andrew Arnott Apr 06 '12 at 02:52
1

Take a look at this post, it explains how to implement a 2 Legged OAuth using DotNetOpenAuth 4 with a Google Apps consumer key + secret.

Google Calendar V3 2 Legged authentication fails

Hope it will helps you :)

Community
  • 1
  • 1
Pedro
  • 3,511
  • 2
  • 26
  • 31