oauth-2-0-setup

name	oauth-2-0-setup
description	Implement OAuth 2.0 authentication flows including authorization code with PKCE, client credentials, and device code for secure API integration. Use when the user requests oauth 2 0 setup or provides relevant inputs for this workflow.
license	MIT
metadata	{"author":"awesome-ai-agent-skills","version":"1.0.0"}

OAuth 2.0 Setup

This skill enables an AI agent to implement OAuth 2.0 authentication for API integrations. The agent selects the appropriate grant type for the use case—authorization code with PKCE for user-facing apps, client credentials for machine-to-machine auth, and device code for input-limited devices. It handles token storage, refresh token rotation, CSRF protection via the state parameter, and secure credential management throughout the flow.

Workflow

1. Select the appropriate grant type: Choose the OAuth 2.0 flow based on the client type. Use authorization code with PKCE for web and mobile apps where a user is present—PKCE replaces the client secret and prevents authorization code interception attacks. Use client credentials for server-to-server communication with no user context. Use device code flow for CLI tools or smart TVs where browser-based login isn't possible. Implicit flow is deprecated and should not be used.

2. Register the application with the provider: Create an OAuth application in the provider's developer console (Google, GitHub, Auth0, etc.). Configure the redirect URI precisely—mismatched URIs are the most common setup error. For PKCE flows, mark the application as a public client. Record the client ID, client secret (if applicable), authorization endpoint, token endpoint, and scopes.

3. Implement the authorization request: Construct the authorization URL with the required parameters: client_id, redirect_uri, response_type=code, scope, and a cryptographically random state parameter for CSRF protection. For PKCE, generate a random code_verifier (43-128 characters), derive the code_challenge using SHA-256, and include both code_challenge and code_challenge_method=S256 in the request. Store the state and code_verifier in the session.

4. Handle the callback and exchange tokens: When the provider redirects back with the authorization code, first verify the state parameter matches what was stored in the session. Then exchange the code for tokens by POSTing to the token endpoint with grant_type=authorization_code, the authorization code, redirect_uri, client_id, and the code_verifier (for PKCE). Parse the response for access_token, refresh_token, expires_in, and token_type.

5. Store tokens securely: Never store tokens in localStorage (XSS vulnerable) or URL parameters (logged in server access logs). Use HTTP-only secure cookies for web apps, the system keychain for desktop apps, and encrypted storage for mobile apps. Store refresh tokens server-side when possible. Record token expiration timestamps so you can proactively refresh before expiry.

6. Implement token refresh and rotation: Before each API call, check if the access token is expired or about to expire (within a 60-second window). If so, use the refresh token to get a new access token. Handle refresh token rotation—when the provider issues a new refresh token alongside the new access token, store the new refresh token and invalidate the old one. If refresh fails with an invalid_grant error, the user must re-authenticate.

Supported Technologies

• Providers: Auth0, Google, GitHub, Microsoft Entra ID, Okta, AWS Cognito, Keycloak
• Server frameworks: Express.js, FastAPI, Django, Spring Security, ASP.NET Core
• Libraries: passport.js (Node.js), authlib (Python), oauthlib (Python), Spring Security OAuth
• Token formats: JWT (self-contained), opaque tokens (require introspection)
• Standards: RFC 6749 (OAuth 2.0), RFC 7636 (PKCE), RFC 8628 (Device Code), RFC 9449 (DPoP)

Usage

Provide the agent with the OAuth provider, the type of application (web app, SPA, CLI, server-to-server), and the required scopes. The agent will select the correct grant type and produce a complete implementation including the authorization flow, token exchange, secure storage, and refresh logic.

Examples

Example 1: Authorization Code Flow with PKCE (Node.js/Express)

const express = require("express");
const crypto = require("crypto");
const session = require("express-session");

const app = express();
app.use(session({
  secret: process.env.SESSION_SECRET,
  resave: false,
  saveUninitialized: false,
  cookie: { secure: true, httpOnly: true, sameSite: "lax", maxAge: 3600000 },
}));

const OAUTH_CONFIG = {
  clientId: process.env.OAUTH_CLIENT_ID,
  authorizationEndpoint: "https://accounts.google.com/o/oauth2/v2/auth",
  tokenEndpoint: "https://oauth2.googleapis.com/token",
  redirectUri: "https://myapp.com/auth/callback",
  scopes: ["openid", "email", "profile"],
};

// Generate PKCE code verifier and challenge
function generatePKCE() {
  const verifier = crypto.randomBytes(32).();
   challenge = crypto
    .()
    .(verifier)
    .();
   { verifier, challenge };
}


app.(,  {
   state = crypto.().();
   { verifier, challenge } = ();

  
  req.. = state;
  req.. = verifier;

   params =  ({
    : .,
    : .,
    : ,
    : ..(),
    : state,
    : challenge,
    : ,
    : ,  
    : ,
  });

  res.();
});


app.(,  (req, res) => {
   { code, state, error } = req.;

   (error) {
    .();
     res.();
  }

  
   (state !== req..) {
    .();
     res.().();
  }

   {
     tokenResponse =  (., {
      : ,
      : { :  },
      :  ({
        : ,
        : code,
        : .,
        : .,
        : req..,
      }),
    });

     (!tokenResponse.) {
       err =  tokenResponse.();
        ();
    }

     tokens =  tokenResponse.();

    
    req.. = tokens.;
    req.. = tokens.;
    req.. = .() + tokens. * ;

    
     req..;
     req..;

    res.();
  }  (err) {
    .(, err.);
    res.();
  }
});


  () {
   (!req..) {
     res.();
  }

  
   (.() > req.. - ) {
     {
       refreshResponse =  (., {
        : ,
        : { :  },
        :  ({
          : ,
          : req..,
          : .,
        }),
      });

       (!refreshResponse.)   ();

       tokens =  refreshResponse.();
      req.. = tokens.;
      req.. = .() + tokens. * ;
      
       (tokens.) {
        req.. = tokens.;
      }
    }  {
      
      req..();
       res.();
    }
  }
  ();
}

app.(, ensureValidToken,  (req, res) => {
   profile =  (, {
    : { :  },
  });
   user =  profile.();
  res.({ :  });
});

app.();

Example 2: Client Credentials Flow (Machine-to-Machine)

import os
import time
import threading
import requests

class ClientCredentialsAuth:
    """OAuth 2.0 client credentials flow for server-to-server auth.

    Manages token lifecycle with thread-safe caching and automatic refresh.
    """

    def __init__(self, token_endpoint: str, client_id: str, client_secret: str,
                 scopes: list[str] | None = None):
        self.token_endpoint = token_endpoint
        self.client_id = client_id
        self.client_secret = client_secret
        self.scopes = scopes or []
        self._access_token: str | None = None
        self._token_expiry: float = 0
        self._lock = threading.Lock()

    def get_access_token(self) -> str:
        """Get a valid access token, refreshing if necessary."""
        with self._lock:
            if self._access_token and time.time() < self._token_expiry - 60:
                return self._access_token
             ._fetch_new_token()

     () -> :
        response = requests.post(
            .token_endpoint,
            data={
                : ,
                : .client_id,
                : .client_secret,
                : .join(.scopes),
            },
            headers={: },
            timeout=,
        )
        response.raise_for_status()
        token_data = response.json()

        ._access_token = token_data[]
        ._token_expiry = time.time() + token_data.get(, )
         ._access_token

     () -> requests.Response:
        
        token = .get_access_token()
        headers = kwargs.pop(, {})
        headers[] = 
         requests.request(method, url, headers=headers, **kwargs)



auth = ClientCredentialsAuth(
    token_endpoint=,
    client_id=os.environ[],
    client_secret=os.environ[],
    scopes=[, ],
)


response = auth.authorized_request(, )
(response.json())


response = auth.authorized_request(, , json={
    : ,
    : ,
})
()

Best Practices

• Always use PKCE for authorization code flows, even for confidential clients. It adds defense in depth against code interception at zero cost. The implicit flow is deprecated—do not use it.
• Validate the state parameter on every callback before processing the authorization code. This is your primary defense against CSRF attacks. Use a cryptographically random value of at least 128 bits.
• Store tokens server-side whenever possible. For web apps, keep tokens in the server session and use HTTP-only, secure, SameSite cookies for the session ID. Never expose access tokens to client-side JavaScript.
• Implement refresh token rotation so that each refresh token can only be used once. When you receive a new refresh token in a token response, immediately replace the old one. If a rotated token is reused, treat it as a compromise and revoke all tokens for that session.
• Request minimum scopes and use incremental authorization when available. Start with the least privilege and request additional scopes only when the user performs an action that needs them.
• Set short access token lifetimes (5-15 minutes for sensitive APIs) and rely on refresh tokens for longevity. This limits the damage window if an access token is leaked.

Edge Cases

• Refresh token expiry: Refresh tokens can expire or be revoked. When a refresh attempt returns invalid_grant, destroy the session and redirect the user to re-authenticate. Do not retry indefinitely.
• Concurrent refresh requests: If multiple threads try to refresh the token simultaneously, only one should perform the refresh while others wait. Use a mutex or single-flight pattern to prevent multiple refresh requests racing and invalidating each other's tokens.
• Provider outages: If the token endpoint is unreachable, continue using the current access token if it hasn't expired yet. Queue retries for token refresh with exponential backoff rather than failing immediately.
• Clock skew: Token expiration checks depend on accurate clocks. Add a buffer (30-60 seconds) when checking expiry to account for clock differences between your server and the OAuth provider.
• Redirect URI mismatch: OAuth providers require exact redirect URI matching. Ensure your registered URI matches exactly, including the protocol, port, and trailing slash. Mismatches cause silent failures that are hard to debug.
• Token leakage in logs: Access tokens appearing in logs, error messages, or URLs are a common vulnerability. Redact tokens in all logging middleware. Never pass tokens as URL query parameters—use Authorization headers exclusively.