Skip to content

Migrate OAuth flow to PKCE - #56

Draft
amurph491 wants to merge 2 commits into
mainfrom
alexmurphy/pkce-oauth
Draft

Migrate OAuth flow to PKCE#56
amurph491 wants to merge 2 commits into
mainfrom
alexmurphy/pkce-oauth

Conversation

@amurph491

@amurph491 amurph491 commented Aug 25, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • replace client-secret OAuth with Authorization Code + PKCE (S256)
  • refresh tokens with team-owned client IDs and explicit auth_flow settings
  • resolve the Codex PreToolUse hook through the installed ${PLUGIN_ROOT} instead of a cwd fallback
  • keep OAuth tokens out of captured stdout and use secure-at-creation settings files with a private managed-workspace handoff
  • add legacy migration guidance, documentation updates, and synchronized 1.9.0 manifests
  • add PKCE, callback, hook, rotation, path-resolution, permission, and runtime regression coverage

Testing

  • PYTHONDONTWRITEBYTECODE=1 python3 tests/test-oauth-pkce.py — 18 passed
  • bash tests/test-check-token.sh — 50 passed
  • bash tests/test-pkce-runtime-guard.sh
  • git diff --check
  • reinstalled local cachebuster build and verified the installed hook with CODEX_PLUGIN_ROOT and CLAUDE_PLUGIN_ROOT unset

Manual follow-up

  • run the credentialed multi-platform end-to-end matrix with team-owned Spotify test applications
  • reauthorize/rotate any refresh token exposed during pre-fix testing

amurph491 and others added 2 commits August 25, 2026 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant