Release v2.3.0 — OAuth 2.1 for claude.ai web + Claude Desktop#24
Merged
Conversation
…s tables Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ha256 hashing Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…with rotation + chain invalidation Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…eware Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…7591) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…6 and EXACT redirect-URI match Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
… refresh token mint Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ection Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Adds setAccessTokenVerifier() to createAuth so the OAuth layer can wire in async JWT verification without a circular dependency. Non-pmd_ bearers go through the verifier first, then fall through to legacy token lookup.
…S metadata Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…JWT_SECRET is set
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…r MCP clients Inspector + claude.ai web run in the browser, so cross-origin fetch to the OAuth token endpoint was blocked (TypeError: Failed to fetch). Wildcard origin is correct here — MCP clients have unknown origins by definition. Allow-Credentials stays unset (Bearer tokens travel via Authorization header, not cookies) and combining wildcard origin with credentials is forbidden by the spec anyway. Phase-1 endpoints (/api/*, /login, /settings) deliberately untouched, plus /oauth/authorize which is a top-level browser redirect, not a fetch source.
Brings the OAuth-2.1 Authorization Code stack (PKCE-S256, DCR, JWT access tokens, opaque rotating refresh tokens, RFC 8414/9728/7591/7009 discovery + lifecycle) onto the v2.x line on top of the multi-user and recipe-engine work that landed in v2.0/v2.1/v2.2. OAuth is opt-in via OAUTH_JWT_SECRET. Without it, behavior is identical to v2.2.x. Closes #6, #10. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- .env.example: OAuth section was labeled "new in v2.1" (carry-over from feat/oauth); ships in v2.3 - MIGRATION.md: remove redundant bottom OAuth section; v2.2.x → v2.3.0 path at top is canonical Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
feat/oauthintomainon top of v2.0 (multi-user), v2.1 (PWA persistence), and v2.2 (site recipe engine).at+jwt), opaque rotating refresh tokens with chain-wide reuse detection, revocation (RFC 7009), and full RFC 8414 / RFC 9728 discovery.OAUTH_JWT_SECRET. Behavior is unchanged from v2.2.x without it.What's in the diff
lib/oauth/— new module (tokens, store, pkce, pages, rate-limit, index)server.js— wires OAuth setup beforecreateApp(...)whenOAUTH_JWT_SECRETis set; recipe-engine bootstrap from v2.2 is preservedlib/auth.js— middleware accepts JWT bearer tokens via injected verifierlib/cache.js— addsoauth_clients,oauth_auth_codes,oauth_refresh_tokenstables alongside the v2.2metatabletest/oauth-*.test.js+test/integration-oauth.test.js— full coverage for PKCE, store, DCR, authorize, token, revoke, CORS, rate-limit, middleware, and end-to-end DCR → authorize → consent → token → API → refreshCHANGELOG.md,MIGRATION.md,README.md,.env.example— docsTag policy
:latestDocker tag stays pinned to v1.2.x. v2.3.0 will be published asaeternalabshq/pullmd:2.3.0,:2.3,:2(Docker Hub + GHCR, multi-arch). The:latestflip remains decoupled from this release.Test plan
node --testgreen locally (558/558 passing)🤖 Generated with Claude Code