Relationships
#4589 Docs: serve now ends links on its own after a leaked client secret
Opened by skunk-ape · 11/10/2026
Closed: merged into #4619, which makes this correction with the customer integration guide and the other serve manual fixes in one PR. It first moved into #4554, whose manual section then moved to #4619.
Follows #4563, which shipped in swamp PR 3712.
What changed
Serve now reads swamp-club's link feed and people read. A link ended on swamp-club reaches serve within about 30 seconds. When swamp-club refuses serve's client (401 invalid_client), serve refuses every delegated request at once, and ends the links once it reads swamp-club again or once the refusal has lasted an hour.
Stale text
content/manual/how-to/swamp-serve/deploy-headless-oauth.md, section "Respond to a leaked client secret", step 3 "End the delegations on the server" opens:
The server does not yet learn that swamp-club ended the links, so it still accepts the delegations' tokens.
That is no longer true. After "Rotate secret" with "End all links", the old secret stops at once, so serve refuses every link within about 30 seconds.
Suggested replacement for that paragraph
Serve refuses these links on its own within about 30 seconds and ends them once it reads swamp-club again. To end them at once, revoke each integration on the server:
Keep the two commands that follow (swamp access integration revoke <integration-id> and swamp access delegation end <delegation-id>) unchanged.
Out of scope
The manual doesn't document the link API for app authors yet. consent_required, relinking (a new consent replaces the old one on the same delegation) and the new refresh reasons (suspended, links_unavailable) belong with whatever first documents that API.
Closed
No activity in this phase yet.