Why OAuth Exists
The scenario everyone recognizes Your application wants to access a user's data on another service — their Google Calendar, GitHub repositories, or company files in SharePoint. The naive approach: ask
Search for a command to run...
Series
The scenario everyone recognizes Your application wants to access a user's data on another service — their Google Calendar, GitHub repositories, or company files in SharePoint. The naive approach: ask
Four roles (memorize these) OAuth names four actors. Everything else hangs off them. Role Plain English Example Resource owner User who can grant access Alice Client App requesting access Yo
The one flow to learn first If you implement only one OAuth flow, make it Authorization Code with PKCE (Proof Key for Code Exchange). It works for: Server-side web apps (Spring Boot, Django, Rails)
The myth "We'll buy Okta / Auth0 / deploy Keycloak — then auth is done." Identity providers (IdPs) and authorization servers solve a specific, hard problem: issuing tokens after authenticating a use
This post is a checklist disguised as war stories Every item below appears in real audits. OAuth did not fail — configuration and application code did. 1. Redirect URI laxity Mistake: Register https:
GitHub: github.com/mnafshin/oauth What we are building A minimal server-rendered Spring Boot web app that: Redirects unauthenticated users to Keycloak Completes Authorization Code + PKCE (Spring ha