Page MenuHomePhabricator

Add a Duo API future
ClosedPublic

Authored by epriestley on Jan 23 2019, 9:33 PM.
Tags
None
Referenced Files
F15503885: D20026.id47802.diff
Mon, Apr 14, 2:08 PM
F15503750: D20026.id.diff
Mon, Apr 14, 12:42 PM
F15502669: D20026.id47834.diff
Mon, Apr 14, 3:03 AM
F15491772: D20026.diff
Sat, Apr 12, 7:22 AM
F15460090: D20026.id47802.diff
Mon, Mar 31, 8:04 PM
F15423460: D20026.id47802.diff
Sat, Mar 22, 3:35 PM
F15422700: D20026.diff
Sat, Mar 22, 10:15 AM
F15389491: D20026.diff
Mar 15 2025, 5:20 AM
Subscribers
None

Details

Summary

Depends on D20025. Ref T13231. Although I'm not currently planning to actually upstream a Duo MFA provider, it's probably easiest to put most of the support pieces in the upstream until T5055.

Test Plan

Used a test script to make some (mostly trivial) API calls and got valid results back, so I think the parameter signing is correct.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

src/applications/metamta/future/PhabricatorTwilioFuture.php
61

This was a leftover from implementing the thing, setPath() wiped it out. I caught it while COPY/PASTING CODE HA HA HA

This revision is now accepted and ready to land.Jan 24 2019, 7:08 PM
This revision was automatically updated to reflect the committed changes.