Page MenuHomePhabricator

Add a Duo API future
ClosedPublic

Authored by epriestley on Jan 23 2019, 9:33 PM.
Tags
None
Referenced Files
F14755596: D20026.id47802.diff
Tue, Jan 21, 4:05 PM
F14751270: D20026.id.diff
Tue, Jan 21, 12:29 PM
Unknown Object (File)
Sat, Jan 18, 2:23 PM
Unknown Object (File)
Sat, Jan 18, 12:40 AM
Unknown Object (File)
Mon, Jan 13, 3:55 PM
Unknown Object (File)
Wed, Jan 1, 4:25 AM
Unknown Object (File)
Dec 5 2024, 10:41 AM
Unknown Object (File)
Dec 3 2024, 2:10 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.