Cutting a person off does not reach the Discourse and FedWiki integrations built into the console #339

Open
opened 2026-11-22 08:54:24 +00:00 by cgalo5758 · 0 comments
Owner

The question

#171 adds a cut-off: from a person's page, an operator ends that person's access everywhere the console reaches, at once. A connected application learns it from the person's desired-state record, which then lists every key off. The Discourse and FedWiki integrations built into the console never read those records. Discourse's sweep picks the members of each group from entitlements (ListDesiredLinkedMembers in internal/integrations/discourse/store/queries/desired_members.sql), and FedWiki's gate in the console reads the same entitlements. A cut-off changes neither. A cut-off person therefore keeps posting on the forum, keeps their wiki sites and can still make new ones, until both integrations move onto the connector protocol (#174).

Should the built-in integrations honour a cut-off before #174, or is it enough that the cut-off's confirmation lists them under "Connections that may still let the person in"?

What depends on the answer

  • In a deployment whose only connected applications are the built-in ones, a cut-off changes nothing the person can reach. Until #174 an operator who cuts someone off has to remove them from the forum and the wiki farm by hand.
  • Any change made for this lands in internal/integrations/discourse and internal/integrations/fedwiki, which #174 deletes.

Options known so far

  • Keep the built-in integrations as they are, and keep the confirmation's list as the warning. Nothing is written that #174 deletes; the operator does the rest by hand.
  • Make each built-in integration read the cut-off: Discourse's sweep leaves a cut-off person out of every group it manages, and FedWiki's gate refuses them, until the cut-off is lifted. Two small changes in code that #174 deletes.
  • Offer the cut-off only once an application it reaches is connected, so that no page offers an act that reaches nothing.

Decided when

The answer is written into the cut-off's spec in #171, and either the built-in integrations honour a cut-off or the confirmation's list stands as the accepted behaviour until #174.

### The question #171 adds a cut-off: from a person's page, an operator ends that person's access everywhere the console reaches, at once. A connected application learns it from the person's desired-state record, which then lists every key off. The Discourse and FedWiki integrations built into the console never read those records. Discourse's sweep picks the members of each group from entitlements (`ListDesiredLinkedMembers` in `internal/integrations/discourse/store/queries/desired_members.sql`), and FedWiki's gate in the console reads the same entitlements. A cut-off changes neither. A cut-off person therefore keeps posting on the forum, keeps their wiki sites and can still make new ones, until both integrations move onto the connector protocol (#174). Should the built-in integrations honour a cut-off before #174, or is it enough that the cut-off's confirmation lists them under "Connections that may still let the person in"? ### What depends on the answer - In a deployment whose only connected applications are the built-in ones, a cut-off changes nothing the person can reach. Until #174 an operator who cuts someone off has to remove them from the forum and the wiki farm by hand. - Any change made for this lands in `internal/integrations/discourse` and `internal/integrations/fedwiki`, which #174 deletes. ### Options known so far - Keep the built-in integrations as they are, and keep the confirmation's list as the warning. Nothing is written that #174 deletes; the operator does the rest by hand. - Make each built-in integration read the cut-off: Discourse's sweep leaves a cut-off person out of every group it manages, and FedWiki's gate refuses them, until the cut-off is lifted. Two small changes in code that #174 deletes. - Offer the cut-off only once an application it reaches is connected, so that no page offers an act that reaches nothing. ### Decided when The answer is written into the cut-off's spec in #171, and either the built-in integrations honour a cut-off or the confirmation's list stands as the accepted behaviour until #174.
cgalo5758 added this to the Public launch milestone 2026-11-22 09:55:13 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#339