Never build a login again : The art of using Social Auth with Django
summary
Claim: stop building auth and delegate it. Walks through three steps that take about an hour: create an app on the provider (Twitter/LinkedIn), install and configure python-social-auth in Django settings and URLs, and drop a provider login button into the template. Concrete demo imports LinkedIn resumes, asks Dropbox permission to store outputs so no user resumes live on servers, and uses provider scopes to grab names and profile data. Shows it speeds development and keeps credentials off the system.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:01Hacker News inspiration
- 2:42Rethinking user management
- 4:20Agility and rapid development
- 5:58Mobile and social login
- 8:11Trust and user security
- 9:27Choosing the right provider
- 12:08Django implementation steps
- 14:47Demo and use cases
- 17:23Q&A and conclusion
related talks
26mDeveloping a Single Sign On Service using Django
26mOAuth2 and Django, What You Should Know
25mUnderstanding Django authentication
19mImpress your enterprise customers with OpenID Connect login
39mAuthentication done right: consuming (and serving) Oauth2.0
38mFinally Understand Authentication in Django REST Framework
01h 38mBooting up Spring Social
40mWhy are you still managing users? Identity has a cloud version