You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Team] Authenticate individual team members and revoke sessions #48
Proposed issue / PR title:feat(auth): add member sign-in and revocable team invitations.
Goal: give the server a trusted human actor for each request and connection.
Scope: a minimal supported sign-in/session flow, expiring single-use team invitations, member removal, session revocation and authenticated actor propagation to core handlers. Reuse the host’s supported authentication facilities where suitable; do not invent custom cryptography. Define how an existing installation is bootstrapped into its first authenticated owner.
Code area: core API/channel integration, client onboarding and the host-auth integration seam; verify the actual DSH facilities before selecting implementation details.
Acceptance and tests: two browsers have different member identities; forged client actor IDs have no effect; invitation replay/expiry fails; removal invalidates existing sessions and live subscriptions. Keep shared-team operation disabled until TODO-D’s authorization lands.
Delivery
One focused implementation PR for this issue. This is planned work, not a claim of shipped multi-human support. Preserve the pristine upstream pin and generated patch/client boundaries. Keep team mode disabled until the documented authorization gates pass. Record exact tested head, executed checks, missing checks and independent review. No production credentials or live deployment are part of this issue.
Activity
feat(auth): member sign-in and revocable invitations (#48)
docs(ds-bot-core): document member-auth foundation (#48)
fix(auth): harden member removal, bootstrap invite, revoke invite (#48)
test(auth): remove ttl flake (#48)
fix(issue-ref): read a bare ThinkFlowLab#1234 only when the number st…