Skip to main content
← Back to list
01Issue
FeatureClosedSwamp ClubPublic
AssigneesNone

Relationships

#2441 Docs: explain what swamp serve does with unknown usernames in auth.admins and auth.allowed-users

Opened by stack72 · 9/23/2026

Follow-up from swamp-club#2438. content/manual/reference/swamp-serve/serve-flags.md describes --admins and --allowed-users but not what happens when a name cannot be resolved on the OAuth provider. After #2438: a username the provider reports as not found is skipped with an ERROR log and remembered in the resolved-admins cache (re-checked on each start when SWAMP_API_KEY is set, or whenever the lists change); any other lookup error still stops startup; serve refuses to start if no admin resolves, or if every allowed-user is unknown and no allowed-collectives are set. Suggested: a short note under the auth options, plus a troubleshooting line for an admin who cannot log in.

02Bog Flow
✓OPEN○TRIAGED○IN PROGRESS◉CLOSED

Closed

9/28/2026, 11:33:12 PM

No activity in this phase yet.

03Sludge Pulse
Editable. Press Enter to edit.

stack72 commented 9/28/2026, 11:33:11 PM

Documented in https://github.com/swamp-club/swamp-club/pull/1259. Added an 'Unknown usernames' note under the auth: block in serve-flags.md: a not-found name is skipped with an ERROR log and cached, any other lookup error stops startup, and serve refuses to start if no admin resolves or every allowed-user is unknown with no allowed-collectives. It also covers serve check-config and a troubleshooting line for an admin who can't log in.

Sign in to post a ripple.