Brief run through on using the Azure ACS service to abstract claims based identity providers such as Google, Facebook, etc with your client applications.
3. Disclaimer I Am Not A Security Expert I Play One Out of Necessity You Can Too
4. Authentication Problem Multiple Usernames and Passwords Quirky Password Requirement Patterns Users Hate This Reduces Conversions (that’s real $$$)
5. Solutions? Customers Create Multiple Accounts Customers Abandon The Purchase Process Social Sign-On? You Can Also Do ADFS (But Where’s the Fun In That?)
6.
7. Users Trust Social Provider http://tinyurl.com/5vgx8f (Just this week!) Traditional -> 25% signups The Rest Just Leave Social Sign On Users Spend More $$$$
8.
9.
10. Write or Find a Library to Manage Each Provider Lots of Work Maintenance Use An Abstraction Enter Azure ACS Supports oAuth, SWT, SAML and other security acronyms No SLA on Dev Portal How To Implement
16. Setup ACS & Integrate In ASP.NET To The Cloud!!
17. Native Mobile? Can’t Store Key on Mobile Device Need to Implement in Browser Control Use SWT - REST MSFT Has an Alpha Signin Control for WP7 http://tinyurl.com/wp7ac
18. About The Sample The Sample Project is Incomplete The Directions Leave Out Points