You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Browser-complete OAuth callback navigation
Fix the authorization page CSP so a successful same-origin form POST may follow its 303 See Other to the exact, already registered and validated OAuth redirect origin. The previous static form-action 'self' policy let the Worker issue a correct redirect but caused Chromium to block the callback navigation and leave the user on the consent page.
Keep the policy narrow: each consent page receives only 'self' plus that request's exact redirect origin, never a wildcard or scheme-wide allowance. Add a real headless-Chrome negative/positive regression proving the old policy blocks the callback and the new policy preserves code and state; retain Worker-level CSP, PKCE, redirect/resource, password, and token tests. Invalid credentials now preserve only the non-secret account name and display an accessible error while never reflecting the password.