Page MenuHomePhabricator

Make Passphrase "token" credentials accessible via the API
ClosedPublic

Authored by epriestley on Nov 15 2016, 5:09 PM.
Tags
None
Referenced Files
F15576747: D16864.id40604.diff
Tue, May 6, 10:30 AM
F15531772: D16864.id40604.diff
Wed, Apr 23, 12:50 PM
F15504789: D16864.id40604.diff
Mon, Apr 14, 8:39 PM
F15460004: D16864.id40607.diff
Mar 31 2025, 7:06 PM
F15458197: D16864.id40604.diff
Mar 30 2025, 9:36 PM
F15457367: D16864.id.diff
Mar 30 2025, 3:55 PM
F15452883: D16864.diff
Mar 29 2025, 7:56 AM
F15424179: D16864.id40607.diff
Mar 22 2025, 8:41 PM
Subscribers

Details

Summary

Fixes T11867. This should really be on the CredentialType itself, but just punt that for now until the API endpoint gets updated. We'll need the actual code here anyway in some form.

Test Plan

Screen Shot 2016-11-15 at 9.07.35 AM.png (252×534 px, 35 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Make Passphrase "token" credentials accessible via the API.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Nov 15 2016, 5:12 PM
This revision was automatically updated to reflect the committed changes.

Hi @epriestley, the T11867 description (but not the title) also mentioned the note credential type. I don't know if you prefer a new ticket, so just in case, here is my comment...

case PassphraseNoteCredentialType::CREDENTIAL_TYPE:
  if ($secret !== null) {
    $material['note'] = $secret;
  }
  break;