OAuth
An open standard protocol that securely delegates access permissions for specific data or features to third-party services without directly sharing passwords. It primarily provides a token-based authorization framework.
Detailed explanation
Why it matters in tool selection
When choosing AI tools or workflow automation tools, OAuth support is key to security. While the API Key method carries a high risk of exposing all account permissions if the key is leaked, OAuth is much safer because it allows you to restrict the scope of permissions to options like 'read-only' and revoke access for specific apps individually at any time.
What to check
- Does it request only the necessary scopes in accordance with the principle of least privilege?
- Does it support the latest security extensions, such as PKCE (Proof Key for Code Exchange)?
- Does it provide an administrative dashboard to revoke authorization?
Example
When a user connects their Google Calendar to an automation tool like 'Zapier', a Google consent screen appears instead of requiring them to enter their Google password. If they only allow the 'view calendar' permission, Zapier can retrieve calendar data using only an 'access token' without needing the password.
Confusing Terms
OpenID Connect (OIDC)
A layer built on top of OAuth 2.0, designed to verify the user's identity (authentication) as well as authorization.
SAML
An XML-based standard primarily used for Single Sign-On (SSO) between internal enterprise systems. In mobile and modern API environments, OAuth is preferred.