dictionary · OAuth
What Is OAuth? Authorization for AI Service Connections
Understand OAuth, authorization versus authentication, access tokens, scopes, and how OAuth supports AI connections using MCP.
Conclusion first
OAuth is an authorization standard for delegating limited access to an external service to another application.
Imagine connecting a document service to an AI application such as ChatGPT. Instead of telling the AI application the service password, a user can approve specific permissions on the document service’s authorization page.
OAuth itself is not an authentication or sign-in protocol. Nor does using OAuth automatically make every operation safe. Delegated permissions and the service’s own access checks both matter.
Definition
The key idea of OAuth is delegating permission rather than sharing an account password.
Giving a third-party app the original service password may grant much more access than the app needs. OAuth enables a user to approve limited access at the original service, after which the connected Client uses an Access Token to request authorized APIs.
An Access Token is sensitive authorization material. It must be protected even though it is not an account password.
How it works
Suppose your documents are stored in an imaginary service called Document Cloud.
- Start a connection: Select the corresponding app from ChatGPT.
- Sign in and authorize: If required, sign in to Document Cloud and review permissions such as read access.
- Receive authorization: The app obtains an Access Token through an OAuth process.
- Request a search: Ask the AI to search for this week’s meeting notes.
- Check access: The document service validates the token and relevant permissions before returning results.
This illustrates a general flow. The actual ChatGPT interface, supported Tools and available plans depend on the connected provider.
Authentication versus authorization
| Concept | What it establishes | Example |
|---|---|---|
| Authentication | Who the person is | Sign-in and identity verification |
| Authorization | Which actions are permitted | Read-only document access |
| OAuth | Delegated authorization | Approving access for an external app |
| OpenID Connect (OIDC) | Authentication built on OAuth 2.0 | Signing in with another service |
Being signed in does not mean every operation is permitted. Similarly, authorizing an integration does not automatically grant access to all documents in an organization.
Four roles in OAuth
| Role | Responsibility | Example |
|---|---|---|
| Resource Owner | Grants access to resources | Person managing documents |
| Client | Requests access | AI-connected application |
| Authorization Server | Issues authorization tokens | Service authorization system |
| Resource Server | Provides protected APIs and data | Document search API |
Authorization Server and Resource Server are distinct roles, not necessarily separate computers.
Access Token, Scope and Refresh Token
Access Token
An Access Token is authorization information a Client uses to request protected APIs. The Resource Server checks validity, intended recipient, lifetime and permitted operations. Treat Access Tokens as secrets.
Scope
Scope expresses the permissions an application requests. Hypothetical examples are documents.read for reading and documents.write for modifying documents. The actual scope names depend on the provider.
An app that only searches documents usually does not need write permission. Even a read scope does not necessarily authorize access to every document: per-resource restrictions still apply.
Refresh Token
Access Tokens usually expire. Some implementations use a Refresh Token to obtain new Access Tokens. Refresh Tokens are not always issued, and revocation or disconnect behavior varies by implementation.
How OAuth relates to MCP
MCP standardizes how AI applications connect to external Tools and data; OAuth can support authorization for those connections.
For an MCP-enabled document search service, MCP can expose and invoke Tools while OAuth handles delegated access to protected resources.
The HTTP authorization model in MCP describes a protected MCP Server acting as a Resource Server and an MCP Client supplying an appropriate Access Token.
However, OAuth is not mandatory for every MCP connection. Local connections and other supported configurations may handle authorization differently. See the Complete Guide to MCP.
What to check on an authorization screen
- Which app is requesting access? Verify the app identity.
- What is being requested? Read-only access may be sufficient; broader edit or delete permission might not be.
- Can access be revoked? Check the original service’s connected-app management options.
AI integrations can use Tools that perform real operations, so reviewing permissions matters.
Commonly confused concepts
Is OAuth a sign-in protocol? Its primary purpose is authorization. OpenID Connect builds authentication capabilities on OAuth 2.0.
Can AI do anything after OAuth connection? No. Tokens and the provider’s own access controls constrain what is permitted.
Does OAuth eliminate token leaks? No. Tokens still require secure handling.
Will adding scopes fix an invisible MCP Tool? Not necessarily. Tool discovery, app settings or connectivity may be responsible. See MCP Tools Not Showing in ChatGPT.
How this relates to OGINAU
OGINAU has tested authentication and authorization while developing OGINAU Remote and OGINAU Browser for connecting AI applications to external environments.
A key lesson is that a person approving a connection and an application being authorized to perform a specific action are different things. A successful connection does not automatically permit access to every file or operation.
This article shares generalizable engineering insights, not proprietary credential handling, permission-evaluation sequences or internal architecture.
Sources and primary information
-
RFC 6749: The OAuth 2.0 Authorization Framework: basic OAuth framework.
-
RFC 9700: OAuth 2.0 Security Best Current Practice: security and token protection.
-
OpenID Connect Core 1.0: authentication based on OAuth 2.0.
-
MCP Authorization (2026-07-28): OAuth and protected MCP resources.
-
OGINAU Remote and OGINAU Browser engineering notes: separating a successful connection from permission to execute an operation.
Summary
OAuth is an authorization standard for delegating limited access without giving a connected application the original service password.
The key distinctions are authentication versus authorization, Access Token versus Scope, and a successful connection versus permission to perform a particular operation.