Skip to content

chore: reset datadog and posthog on logout - #13

Merged
disintegrator merged 1 commit into
mainfrom
logout-telemetry-wipe
Aug 7, 2025
Merged

chore: reset datadog and posthog on logout#13
disintegrator merged 1 commit into
mainfrom
logout-telemetry-wipe

Conversation

@disintegrator

Copy link
Copy Markdown
Contributor

This change ensures no state is left behind for PostHog and DataDog RUM after users log out.

@disintegrator
disintegrator requested a review from a team as a code owner August 7, 2025 15:33
@vercel

vercel Bot commented Aug 7, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
gram ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 7, 2025 3:36pm
gram-landing ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 7, 2025 3:36pm

This change ensures no state is left behind for PostHog and DataDog RUM
after users log out.
@disintegrator
disintegrator merged commit 74a1faf into main Aug 7, 2025
10 checks passed
@disintegrator
disintegrator deleted the logout-telemetry-wipe branch August 7, 2025 15:38
@claude claude Bot mentioned this pull request Oct 1, 2025
qstearns added a commit that referenced this pull request May 12, 2026
…dings

Security:
- Sec #1: Auth-code redemption is now atomic via Redis GETDEL (new
  Cache.GetAndDelete). Two clients racing on the same code can't both win.
- Sec #14: Consent-state consumption uses the same GETDEL primitive,
  preventing parallel POSTs from minting multiple grants per /authorize.
- Sec #13: ValidateBearer fails closed on revocation-cache errors (Redis
  outage → tokens reject, not admit).
- Sec #4: /revoke verifies the presented token belongs to the
  authenticated client (RFC 7009 §2.1). Ownership mismatches look like
  the "unknown token" silent-no-op per §2.2. New GetUserSessionByJTI
  and GetUserSessionByRefreshTokenHash peek queries support this.
- Sec #9: JWT audience is now urn.NewToolset(toolset.ID) — globally
  unique even when slugs collide across projects. No cross-project
  token replay.
- Sec #11: JWT iss claim honours custom domains (matches the AS
  metadata document's issuer).

Correctness:
- Bug #2: Access-token lifetime is hardcoded (1h). issuer.SessionDuration
  is now the refresh-token (i.e. total session) lifetime — the value the
  IDP-driven session window was meant to control.
- Bug #5: HandleIDPCallback forwards IDP error responses back to the MCP
  client's redirect_uri instead of swallowing them as a generic 400.
- Bug #6: Consent POST refuses to mint an anonymous session for a
  private toolset — IDP authentication is required first.
- Bug #8: Consent approve path requires action=approve explicitly.
  Missing or unknown values 400, not fail-open into the approval branch.
- Bug #10: HandleToken now calls requireUserSessionIssuer like the
  other authn-dance handlers.
- Bug #15: Consent POST → GET redirects use 303 See Other (was 302
  Found, which leaves the verb implementation-defined).

Hardening:
- Hard #3: isUniqueViolation uses errors.As + *pgconn.PgError.Code
  instead of strings.Contains on the error message.
- Hard #7: Migrate the remaining "jwt-signing-key" literal callsites
  (chatsessions/assistanttokens/assets) to usersessions.JWTSigningKeyFlag.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants