Posted on: 12/10/2013 11:51:58 AM | Views : 923

Hi all,
I have been looking through and trying out the various tutorials related to Web API 2 security but have not found what I am looking for (or have not recognised it if I have seen it).
Other than the example on Individual Accounts in Web API found here (http://www.asp.net/web-api/overview/security/individual-accounts-in-web-api) all the examples I have found seem to concentrate on client websites using the external providers (e.g. Microsoft, Facebook, Google etc) but not passing that authentication onto a Web API service.
What I want to know is the pattern I should follow to allow a user on a client site (A) to login using one of the external provider and then access the services on a REST service authored using Web API 2 (site B). 
Would you for example have a database for the Client site with a membership database that is used to capture the nece ...

Go to the complete details ...