OAuth 2.0 Roles: Resource Owner, Client, Authorization Server
You'll learn the four distinct roles that interact in every OAuth 2.0 authorization flow.
The Four Pillars of OAuth 2.0
OAuth 2.0 defines exactly four roles that work together to grant access to protected resources without sharing passwords. Think of these as actors in a carefully choreographed play—each has a specific job.
Resource Owner
The resource owner is typically the end user who owns the data. This is you when you click "Sign in with Google" on a third-party app—you own your Google calendar, photos, or contacts. The resource owner has the authority to grant or deny access to their protected resources.
Client
The client is the application requesting access to the resource owner's data. When you use a calendar app that wants to read your Google Calendar, that calendar app is the client. Importantly, the client could be a web app, mobile app, or even a server-side service—but it's always the one asking for permission.
Authorization Server
The authorization server issues access tokens to the client after successfully authenticating the resource owner and obtaining their authorization. In the Google example, Google's authorization server verifies your identity and asks, "Do you allow Calendar App X to read your calendar?" If you consent, it issues a token to the client.
Resource Server
The resource server hosts the protected resources and accepts access tokens to serve requests. This is often the same entity as the authorization server (like Google's API servers), but conceptually it's separate—it validates tokens and returns the actual data.
The Flow
Resource Owner authorizes → Authorization Server issues token → Client uses token → Resource Server validates and responds.
Key Takeaway: OAuth 2.0 separates concerns into four roles: the resource owner (user), client (requesting app), authorization server (issues tokens), and resource server (protects data)—enabling secure delegated access without password sharing.