Glossary Term Authentication & APIs

OAuth

A standard way to let users sign in with another service, or let one app access another service on a user’s behalf, without handing over the user’s password.

#security #auth

When this matters

OAuth shows up when you want one-click login, or when your app needs permission to read a user’s Google Calendar, GitHub repos, or Slack workspace. It matters because the setup is easy to underestimate and usually involves callback URLs, scopes, and redirect handling.

Small example

A typical OAuth flow sends the user to a provider, then the provider redirects back to your app with a temporary code your server exchanges for tokens.

1. User clicks "Continue with GitHub"
2. GitHub asks for permission
3. GitHub redirects to /auth/callback?code=...
4. Your server exchanges the code for tokens
5. Your app creates a signed-in session

Common mistake or lookout

Mixing up authentication and authorization. OAuth can help you prove identity, request permissions, or both depending on the setup, but it is not just a fancy password box and it needs the correct provider config in every environment.

Why this matters for vibe coders

For vibe coders, OAuth is often the first place where “the AI built it” collides with real production constraints. One wrong callback URL or mismatched environment value and your login flow turns into an infinite redirect carnival.