Tackling Authentication with Phoenix
summary
Claims that many passwords are trivially compromised—some cracked within six hours—and 66.5% password reuse motivates moving beyond passwords to specific tools and flows: using coyote TOTP for one‑time codes (compatible with Google Authenticator), issuing JWT stateless auth to avoid session stores and extra DB lookups, and using Guardian pipelines to verify tokens per request. A small library called keeper exists as an experiment and the demos report that the approach works in practice.
AI-written summary · about
chapters (41)
- 0:00Intro
- 1:10Passwords
- 2:17Killers Mind
- 2:55Clients
- 3:45Changing technologies
- 4:26Virtual Reality
- 4:52Security
- 5:39Ramona
- 6:43Usability
- 7:19Modification
- 9:30Registration
- 10:42Another great library
- 11:50Request Phase
- 12:25Strategies
- 13:20Cell Phone
- 13:50Password Problem
- 14:01Coyote
- 15:15The Secret
- 15:37The Good Stuff
- 16:03Optimization
- 16:28A Good Diary
- 16:43How Authentication Works
- 16:59Session Cookies
- 17:32Patient
- 17:57JSON Hash
- 18:34Three Parts
- 19:32Request
- 19:50Stateless
- 20:20payload
- 20:35plan
- 20:58JSON web token
- 21:11Local storage
- 21:35Web tokens
- 22:25Guard
- 23:09SignIn
- 25:06Battery Problem
- 25:51JSON Web Tokens
- 26:09Portal
- 26:46The Debate
- 27:17The Keeper
- 28:03Learning Easier with the Ripe
related talks
51mThe state of passwordless auth on the web
47mThe state of passwordless auth on the web
30mGoing Beyond Passwords: The Future of User Authentication
41mThe state of passwordless auth on the web
30mThe State of Passwordless Auth on the Web
38mForgot Password? Yes I Did!
42mChallenges in User Authentication: Balancing Security & User Experience
17mGoing Beyond Passwords: The Future of User Authentication
