Page MenuHomePhabricator

Improve handling of "Deny" responses from Duo
ClosedPublic

Authored by epriestley on Jan 30 2019, 5:18 AM.
Tags
None
Referenced Files
F13218988: D20065.id47929.diff
Sat, May 18, 2:24 PM
F13185676: D20065.diff
Sat, May 11, 3:08 AM
Unknown Object (File)
Tue, May 7, 7:02 AM
Unknown Object (File)
Tue, May 7, 5:36 AM
Unknown Object (File)
Sun, May 5, 8:55 AM
Unknown Object (File)
Fri, May 3, 3:21 AM
Unknown Object (File)
Wed, May 1, 3:11 PM
Unknown Object (File)
Tue, Apr 30, 5:09 PM
Subscribers
None

Details

Summary

Ref T13231. See https://discourse.phabricator-community.org/t/duo-integration-crashes-if-user-is-not-enrolled-and-enrollment-is-disabled/2340/5

(There's an actual bug here, although I'm not sure exactly what's going on on the Duo side in the report.)

Test Plan

To reproduce this, I was only able to actually "Deny" my account explicitly in Duo.

  • With "Deny", tried to add a factor. Got a nice helpful error message.
  • Undenied, added a factor, re-denied, tried to pass an MFA gate. Got another nice helpful error message.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

amckinley added inline comments.
src/applications/auth/factor/PhabricatorDuoAuthFactor.php
386–387

"The The"

This revision is now accepted and ready to land.Jan 31 2019, 2:45 AM
This revision was automatically updated to reflect the committed changes.