2-legged

Now, we have an application with Google Docs Api and 2 legged oauth. However,we want to migrate to Google Drive Api which uses Oauth 2.0. Can we use 2 legged oauth with Google Drive Api? Is there any example? You should use Service Accounts: https://developers.google.com/accounts/docs/OAuth2ServiceAccount I just started looking into this and if I have any luck I will provide more info. However, if you are using 2 legged oauth so you can work with google apps domain-wide then there is a published guide. I believe this is what the other answer was talking about. Blog post explaining domain wide

I'm trying to find my way around the OAuth spec, its requirements and any implementations I can find and, so far, it really seems like more trouble than its worth because I'm having trouble finding a single resource that pulls it all together. Or maybe it's just that I'm looking for something more specialized than most tutorials. I have a set of existing APIs--some in Java, some in PHP--that I now need to secure and, for a number of reasons, OAuth seems like the right way to go. Unfortunately, my inability to track down the right resources to help me get a provider up and running is

I am trying to create an Authentication Module in CSharp where I need to verify the Signature from the request using DotNetOpenAuth(DNOA) Library for 2 Legged OAuth which only has consumer Key and a Secret. If you have any sample implementation of 2 Legged OAuth using DNOA that would be helpful. If not, any ideas on how to implement would work too. Any help would be much appreciated. I wasn't able to get DNOA to work with 2-legged OAuth so I ended up making my own consumer using http://oauth.googlecode.com/svn/code/csharp/OAuthBase.cs as my base class to handle the signature signing. All you

In OAuth 1.0, 2-legged is pretty easily: Simply send the request as usual and omit the access_token header. Things seems to have changed in OAuth 2.0 (drastically, as I found out today :)). In OAuth 2.0, the request no longer has headers such as the nonce, consumer key, timestamp etc. This is just replaced by: Authorization: OAuth ya29.4fgasdfafasdfdsaf3waffghfhfgh I understand how 3 legged authorizations work in OAuth 2.0 and the application flows. But how does 2-legged work in 2.0? Is it possible to design an API that can support both 2-legged and 3-legged OAuth 2.0? I have been searching