Geek Answers Handbook

What is better for ASP.NET MVC REST API? OAuth 2.0 or OAuth 1.0?

We create a REST API using ASP.NET MVC. This API is basically the same as the Factual v3 API. They use two-legged Oauth 1 for their API. Our design is very similar to these applications, primarily the mobile will use our API behind the scenes to provide the service. The end user of the application will not know about our API and therefore will not have any credentials. Therefore, redirecting a user through a browser window to an auth form (e.g. facebook) makes no sense. My questions...

  • Why is OAuth2 flow best used in this scenario?
  • Should we use Oauth2 or just stick with two-way OAuth 1?

For reference, we use C # /. NET, ASP.NET MVC 3 and plan to use DotNetOpenAuth v4.

http://developer.factual.com/display/docs/Factual+Developer+APIs+Version+3

+5
source share
2 answers

Why is OAuth2 flow best used in this scenario?

It's not obligatory. OAuth 2 is an incomplete specification. If you need maximum compatibility, OAuth 1.0 is the best choice (for now). OAuth 2 is easier for the client, due to significantly greater complexity on the server.

Should we use OAuth2 or just stick with two-way OAuth 1?

, , . , DotNetOpenAuth, OAuth 1.0 , OAuth 2.0 , , , .

+4

More articles:


All Articles