Page MenuHomePhabricator

Generate and use "cluster" Conduit API tokens
ClosedPublic

Authored by epriestley on Dec 13 2014, 6:23 PM.
Tags
None
Referenced Files
F15539194: D10990.id26398.diff
Fri, Apr 25, 12:04 AM
F15534786: D10990.id26385.diff
Thu, Apr 24, 2:06 AM
F15532986: D10990.id.diff
Wed, Apr 23, 5:50 PM
F15528178: D10990.diff
Tue, Apr 22, 9:38 AM
F15489809: D10990.diff
Fri, Apr 11, 12:30 PM
F15456428: D10990.id26385.diff
Sun, Mar 30, 9:37 AM
F15455922: D10990.id.diff
Sun, Mar 30, 5:44 AM
F15429963: D10990.id26398.diff
Mar 24 2025, 5:04 AM
Subscribers

Details

Summary

Ref T5955. Ref T2783.

  • Removes the "temporary" type. I was going to use this for T3628 but it started taking more time than I wanted to spend on it.
  • Add a "cluster" type, which is an internal-only token type used within a cluster. This token value is never shown to the user.
  • Automatically generate, use, and cycle cluster tokens.
Test Plan
  • Diffusion (mostly) works with a repository configured to use a remote service.
  • Saw cluster tokens generate; terminated a cluster token and saw it regenerate.
  • Viewed cluster token in settings panel and saw nice explanatory text instead, as expected (we might just hide these eventually).

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable