Page MenuHomePhabricator

Perform a client-side redirect after OAuth server authorization
ClosedPublic

Authored by epriestley on Mar 6 2018, 6:31 PM.
Tags
None
Referenced Files
F22733539: D19177.id45935.diff
Sun, Oct 4, 8:05 AM
F22733534: D19177.id45935.diff
Sun, Oct 4, 8:05 AM
Unknown Object (File)
Aug 25 2026, 12:39 AM
Unknown Object (File)
Aug 23 2026, 12:48 PM
Unknown Object (File)
Aug 11 2026, 9:24 PM
Unknown Object (File)
Mar 29 2026, 12:35 PM
Unknown Object (File)
Feb 27 2026, 10:45 PM
Unknown Object (File)
Dec 16 2025, 9:15 AM
Subscribers
None

Details

Summary

Ref T13099. See that task for discussion. Chrome is unhappy with an MFA form submitting to an endpoint which redirects you to an OAuth URI.

Instead, do the redirect entirely on the client.

Chrome's rationale here isn't obvious, so we may be able to revert this at some point.

Test Plan

Went through the OAuth flow locally, was redirected on the client. Will verify in production.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Draft.Mar 6 2018, 8:18 PM
This revision was automatically updated to reflect the committed changes.