GitHub

GitHub OAuth2

Authorization Code Exchange for web and mobile — GitHub OAuth App setup, API reference, and frontend examples.

Overview

GitHub login is optional and controlled by GITHUB_AUTH_ENABLED. When disabled, GitHub endpoints return 503 Service Unavailable. JWTs are never placed in the redirect URL; the API issues a one-time exchangeCode (Redis, 60 seconds). The same POST /auth/exchange endpoint is shared with Google.

  • • Feature-flagged via environment
  • • Passport GitHub strategy + GithubAuthGuard
  • • Redirect allowlist prevents open redirects
  • • Same token response shape as POST /auth/login

GitHub Developer Settings

Create an OAuth App under GitHub → Settings → Developer settings → OAuth Apps. Set Authorization callback URL to match GITHUB_CALLBACK_URL.

  1. Open https://github.com/settings/developers → OAuth Apps → New OAuth App
  2. Set Application name and Homepage URL
  3. Set Authorization callback URL (e.g. http://localhost:3000/api/v1/auth/github/callback)
  4. Copy Client ID and generate a Client Secret into your .env
  5. Ensure the user grants the user:email scope (required for email)

Environment variables

Loaded from .env via src/config/github-oauth.config.ts (namespace githubOAuth on ConfigService). See .env.example.

Environment.env
GITHUB_AUTH_ENABLED=true
GITHUB_CLIENT_ID=your-github-client-id
GITHUB_CLIENT_SECRET=your-github-client-secret
GITHUB_CALLBACK_URL=http://localhost:3000/api/v1/auth/github/callback
GITHUB_REDIRECT_ALLOWLIST=myapp://success,http://localhost:5173/auth/callback
GITHUB_OAUTH_DEFAULT_ROLES=

Default roles for new GitHub users

New GitHub users receive roles: [] by default (same as password register). Set GITHUB_OAUTH_DEFAULT_ROLES in .env to a comma-separated list of Role values (e.g. user or user,manager). Existing users linked by email keep their current roles.

Sequence

  1. Client opens GET /api/v1/auth/github?redirect=<allowlisted URL>
  2. User consents on GitHub; browser hits GET /api/v1/auth/github/callback
  3. API upserts user, stores exchangeCode in Redis, redirects to redirect?code=...
  4. Client POSTs { code } to /api/v1/auth/exchange and receives JWTs

API reference

1. Start OAuth

Opens GitHub consent. Query redirect must match a prefix in GITHUB_REDIRECT_ALLOWLIST (or omit to use the first allowlist entry).

HTTPGET /api/v1/auth/github
GET /api/v1/auth/github?redirect=http%3A%2F%2Flocalhost%3A5173%2Fauth%2Fcallback

400 invalid redirect · 503 feature disabled

2. Callback

Handled by the API. Redirects to your app with ?code= (or &code= if the URL already has a query).

HTTPGET /api/v1/auth/github/callback
GET /api/v1/auth/github/callback?code=GITHUB_AUTH_CODE&state=...
→ 302 Location: http://localhost:5173/auth/callback?code=EXCHANGE_CODE

3. Exchange code

Public endpoint shared with Google. Consumes the code (single use) and returns the same shape as login.

HTTP RequestPOST /api/v1/auth/exchange
POST /api/v1/auth/exchange
Content-Type: application/json

{
  "code": "EXCHANGE_CODE"
}
HTTP Response200 OK
{
  "user": {
    "id": "...",
    "email": "[email protected]",
    "firstName": "Jane",
    "lastName": "Doe",
    "roles": [],
    "githubId": "1082...",
    "isActive": true
  },
  "accessToken": "eyJhbGciOiJIUzI1NiIs...",
  "refreshToken": "eyJhbGciOiJIUzI1NiIs..."
}

401 invalid/expired/used code · 503 social auth disabled

Frontend — Web (SPA)

Typical flow: button starts OAuth in the same window (or popup); a callback route on your frontend origin reads code from the query string and calls exchange.

JavaScriptStart GitHub login
const API = 'http://localhost:3000/api/v1';
const redirect = encodeURIComponent(
  'http://localhost:5173/auth/callback'
);

// Full-page redirect to Nest → GitHub → back to SPA
window.location.href = `${API}/auth/github?redirect=${redirect}`;
JavaScriptCallback page /auth/callback
// /auth/callback on the SPA
const params = new URLSearchParams(window.location.search);
const code = params.get('code');
if (!code) throw new Error('Missing exchange code');

const res = await fetch('http://localhost:3000/api/v1/auth/exchange', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({ code }),
});
if (!res.ok) throw new Error(await res.text());

const { user, accessToken, refreshToken } = await res.json();
// persist tokens as your app requires
sessionStorage.setItem('accessToken', accessToken);
console.log('signed in', user.email);
  • • Add your frontend callback URL to GITHUB_REDIRECT_ALLOWLIST (e.g. http://localhost:5173/auth/callback)
  • • GITHUB_CALLBACK_URL must point at the Nest API, not the SPA
  • • Store accessToken / refreshToken securely (memory + httpOnly cookie patterns as you prefer)

Frontend — Mobile (deep link)

Use a custom scheme (or universal link) in the allowlist. After GitHub, the API redirects to myapp://success?code=.... The app opens, parses the code, and calls exchange.

React NativeOpen OAuth in browser
import * as Linking from 'expo-linking';
import * as WebBrowser from 'expo-web-browser';

const API = 'https://api.example.com/api/v1';
const redirect = encodeURIComponent('myapp://success');

async function signInWithGitHub() {
  const url = `${API}/auth/github?redirect=${redirect}`;
  await WebBrowser.openAuthSessionAsync(url, 'myapp://success');
}
React NativeHandle deep link + exchange
import * as Linking from 'expo-linking';

async function exchangeFromUrl(url) {
  const { queryParams } = Linking.parse(url);
  const code = queryParams?.code;
  if (!code) return;

  const res = await fetch(`${API}/auth/exchange`, {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({ code }),
  });
  const data = await res.json();
  // data.accessToken, data.refreshToken, data.user
  return data;
}

Linking.addEventListener('url', ({ url }) => {
  exchangeFromUrl(url);
});
  • • Register the scheme in the OS / Expo app.json
  • • Prefer Linking.addEventListener('url', ...) and getInitialURL()
  • • Exchange over HTTPS against your API base URL

Security notes

  • • Redirect URLs must match GITHUB_REDIRECT_ALLOWLIST prefixes
  • • Exchange codes are single-use and expire in 60 seconds (Redis)
  • • Existing local users are linked by verified GitHub email (githubId set; roles unchanged)
  • • GitHub-only users have password null — password login / change-password will fail until a password is set
  • • Email permission is required; login fails if GitHub does not return an email

User model

Postgres entity / interface fields used by GitHub login:

  • • githubId — unique nullable GitHub subject ID
  • • password — nullable for OAuth-only accounts
  • • isActive — set true for new GitHub users
  • • roles — from GITHUB_OAUTH_DEFAULT_ROLES env (default [])

Related