1

I have a website, which contains huge user information. I would like to share these users information using OAuth to third parties users/websites. I found some of the questions related to my requirement, but those were not clear for me. (oAuth ASP.NET Membership Provider). I would like to use dot net OAuth for authentication. My Queries are as follows.

  1. How we can implement an authentication mechanism when the client request an API service. For authentication probably client may need some sort of consumers keys. How they will get those keys. Any registration is needed ?

  2. Do I need to manually maintain any data base for storing the consumers keys/Secret Keys/
    Token Detais Or will it handled Automatically.

I have only rough idea about this kind of authentication. So detailed help will be helpful for me.

Thanks.

Community
  • 1
  • 1
Kurisinkal
  • 53
  • 8
  • You might want to consider something simpler unless you really need all the features of OAuth. See [OAuth 2.0 - Looking Back and Moving On](http://vimeo.com/52882780) – Dustin Kingen May 13 '13 at 11:48
  • Right now I dont need all the features of OAuth. But eventually I may need all. So can't consider another option. – Kurisinkal May 13 '13 at 11:59
  • Well then start reading the [OAuth 2.0 RFC](http://tools.ietf.org/html/rfc6749) because it'll be a long painful journey. – Dustin Kingen May 13 '13 at 12:04
  • You need to handle EVERYTHING yourself since your rollng out your own OAuth provider. – Security Hound May 13 '13 at 12:18

0 Answers0