Presented this in Sweden recently to review the scenarios where Social Login is most powerful and those technical things required to set it up.

1. The Power of
Social Login
Michele Leroux Bustamante
michelebusta@solliance.net

3. Why Social Login?

4. Conversion

5. Company Perspective
• Customers won’t register
• Customers won’t come back
• Acquire new customers
• Easier for customers to engage
• Social login is modern
• Improved registration, target marketing

6. Don’t Suck So Much

7. User Perspective
• Long passwords suck
• Security questions suck more
• Login process sucks
• Registration sucks more
• Unwanted marketing REALLY sucks

8. Fewer passwords
to remember

9. WORST PASSWORD
WINNER 2012
password

10. WORST PASSWORD
WINNER 2013
123456

11. WORST PASSWORDS
TOP 3 FOR 2013
123456
password
12345678

12. DEMO
Setting Up Social Login

13. Don’t Make Me Login Again!

15. Setting up Social

16. Twitter Setup
• apps.twitter.com
– create an app
– get the app key and secret
• Redirect and login
– User asked to authorize during login
– Authorization code returned
– Application uses code to request an access
token
– Application uses access token to interact with
provider API

19. Facebook Setup
• developers.facebook.com
– Create an app
– Get the app id and secret
• Redirect and login
– Users asked to authorize during login
– Authorization code returned
– Application uses code to request info

22. Google
• Uses OpenID Connect
• No app required, url based

23. Share

24. Social Sharing
• Share directly from JavaScript
– Generate sample buttons at provider site
– Customize as desired
• Share through API
– Requires access token to operate on behalf
of the user

26. DEMO

27. Don’t Over Share

30. Connecting Accounts
• Goal to have a single profile
• Login with one or more provider, same
user profile
• Share with one or more provider,
irrespective of login

33. DEMO

34. Let’s Get To Know Each
Other First

35. Long…

36. Too long…

37. Wayyy too long…

38. All you need is
username and
password at
first…

39. If you really
need the
service…you
MAY get away
with a little
more…MAYBE

41. Design Decisions
• Which providers will you support?
• What profile information do you need?
• What sharing options / methods?
• How do you want to handle providers?

42. What if it could
be easier?

43. One Example

50. Value Add w/Auth Providers
• Delegate logic for password strength,
security questions
• Delegate concerns over protecting
credentials (#heartbleed)
• Delegate work to integrate your
customers’ favorite social login network

51. Development Platforms

52. Access to millions
of new users

53. As of October 29, 2013
• Facebook 1.2 B
• Google+ 540 M
• TW 500 M
• LinkedIn 300 M
• Yahoo 300 M
http://www.nydailynews.com/news/national/google-540m-
monthly-users-lags-behind-facebook-article-1.1500403

56. THANK YOU

57. Michele Leroux Bustamante
Managing Partner
Solliance (solliance.net)
CEO and Cofounder
Snapboard (snapboard.com)
Microsoft Regional Director
Microsoft MVP
Author, Speaker
Pluralsight courses on the way!
Blog: michelebusta.com
michelebusta@solliance.net
@michelebusta