docs(plans): Slack as the second installable connector — design note (TASK-006) - #1535
Merged
Merged
Conversation
…d the one secret that enters outside the activation CAS
…he right one: session nonce + confirm-in-Commonly before any bind routes (Vera)
…d why token rotation stays off
…conciler goes on the scheduler (Vera)
…the uncited same-token claim from the crash path
…processes) and a key ring with a re-wrap path (Vera)
…ale processing is taken over by CAS (Vera)
… time — no digest Matches #1537 b801a6e. The hashed cookie was CodeQL's js/insufficient-password-hash (#1779) on every digest variant, and the hash defended against nothing: a row reader already holds state in the same document. Confirm is the wall. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Design note for TASK-006, written against ADR-025 (D1–D17) and the merged Telegram plan as built by #1527 and #1531.
Slack is Telegram with two substitutions:
stateis the connect code and the callback is the enable command. Activation mints the same 128-bit, 10-minute, single-use code; the page renders an Authorize in Slack link carrying it asstate; the unauthenticated callback verifies it before the exchange and binds team, Slack user and the bot DM. Identity is stamped at projection, as today.config.botTokenRef(aConnectorSecretrow, AES-256-GCM under a key from theapi-keysExternalSecret); never returned by any route; revoked on uninstall.Everything else — manifest shape, claim/activation lifecycle, projectors, reconciler, dispatcher selection, page states, #1297 security carry-over — is reused unchanged. The one change Slack forces in #1527's code is the dispatcher no longer naming Telegram.
Also covers: DM-only binding (D8/D15), threads as D11's router, a single
/commonlyslash command for the control plane, Slack's 3-second ack andevent_iddedupe, acceptance seeds for Vera's plan including the stranger smoke, sizes and sequence.Verification
Docs only. Sequence: Vera's verification plan on this note → Kai builds (one backend PR, one page PR, stacked).