Page MenuHomePhabricator

Give Duo MFA a stronger hint if users continue without answering the challenge
ClosedPublic

Authored by epriestley on Feb 5 2019, 2:41 AM.
Tags
None
Referenced Files
F19943873: D20088.id48001.diff
Thu, Apr 16, 6:59 AM
F19926197: D20088.diff
Tue, Apr 7, 3:36 PM
F19874992: D20088.id48001.diff
Mar 16 2026, 12:38 AM
F19264139: D20088.id48001.diff
Dec 22 2025, 6:43 PM
F18826729: D20088.id48001.diff
Oct 24 2025, 5:26 AM
F18782383: D20088.diff
Oct 13 2025, 1:23 AM
F18768635: D20088.diff
Oct 8 2025, 4:36 AM
F18566971: D20088.id.diff
Sep 9 2025, 3:04 PM
Subscribers
None

Details

Summary

See PHI912. Also, clean up some leftover copy/pastey code here.

Test Plan

Screen Shot 2019-02-04 at 6.37.46 PM.png (420×881 px, 45 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

src/applications/auth/factor/PhabricatorDuoAuthFactor.php
678–712

This stuff came from SMS/TOTP but isn't relevant for Duo. We have to return an empty result to make some other code work, although perhaps some future followup could simplify this a bit further.

This revision is now accepted and ready to land.Feb 5 2019, 8:08 PM
This revision was automatically updated to reflect the committed changes.