Page MenuHomePhabricator

Add a Duo API future
ClosedPublic

Authored by epriestley on Jan 23 2019, 9:33 PM.
Tags
None
Referenced Files
F19520580: D20026.id47834.diff
Fri, Jan 16, 3:05 PM
F19517864: D20026.diff
Thu, Jan 15, 4:16 PM
F19517855: D20026.diff
Thu, Jan 15, 4:12 PM
F19517841: D20026.diff
Thu, Jan 15, 4:07 PM
F19503837: D20026.diff
Fri, Jan 9, 1:58 AM
F19468792: D20026.diff
Sun, Jan 4, 10:19 AM
F19468790: D20026.diff
Sun, Jan 4, 10:19 AM
F18866832: D20026.id47802.diff
Nov 3 2025, 7:43 PM
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.