Adventures in Federating Authorization and Authentication with OAuth
summary
Describes federating OAuth to handle 30,000 concurrent requests and a site that’s roughly 90% read-only; evaluates Doorkeeper + Devise + OmniAuth and rejects installing Doorkeeper on one service per microservice. Builds a central Doorkeeper auth service, adds cache-delegation with Redis on each service to validate tokens locally, and load tests to 30,000 concurrent requests with no breakage. Calls out short-lived auth codes, token management pain, and an exposed Doorkeeper admin UI risk.
AI-written summary · about
chapters (6)
- 0:00Start
- 7:00What is Federation
- 14:14Half Requires RAILSCONE Authenication/ Authorizaztion
- 15:12Needs To Scale
- 28:33Under Load
- 32:37It's a Standard
related talks
36mService Oriented Authenication
18mMake Auth great again with Ory
20mPass On Access: User to User Data Sharing With OAuth
56mLock That Sh*t Down!
39mAuthentication done right: consuming (and serving) Oauth2.0
01h 00mSupercharging OAuth 2.0 Security
31mAuthentication/Authorization Starters Battle
55mSupercharging OAuth 2.0 security