Skip to content

v0.3.1: principal-aware Pipedream policy + Teams attribution

Choose a tag to compare

@tomascupr tomascupr released this 30 May 21:44
· 21 commits to main since this release

A correctness and dual-identity release that closes the two security findings deferred from v0.3.0.

Fixed

  • Per-user Pipedream policy is now enforced by principal. evaluateToolOnly, the gate behind every Pipedream plugin surface (policy check, Connect token, action discovery), was principal-blind: it matched tool policies on tool plus action only. A policy an admin scoped to a single Slack or Teams user or role was therefore enforced for everyone (a scoped deny over-blocked the whole workspace; a scoped allow over-granted). The principal-aware tool-policy gate that the dashboard already used is now shared by both surfaces, so a scoped grant only applies to a matching principal and a scoped grant with no match denies instead of falling through to a global allow.

  • Microsoft Teams actors are attributed correctly. The plugin keyed every Pipedream principal as a Slack id, so Teams (msteams) users were mislabeled end to end: audited as Slack actors and unmatchable by Teams-scoped policy. The plugin now forwards a platform-neutral principal id and the control plane resolves the platform from its shape (Teams AAD ids are UUIDs, Slack ids are not), threading it through both policy evaluation and audit. A new indexed actor_teams_aad_user_id audit column (migration 012) makes Teams actors attributable and queryable, mirroring actor_slack_user_id.

Per-user Pipedream Connect OAuth isolation, tool policy, and audit now all key on the active chat user's principal on both Slack and Teams.

Notes

  • Adds migration 012_audit_actor_teams_aad_user_id.sql (append-only; applied automatically on boot).
  • The internal plugin wire field slackUserId is renamed to principalId across the plugin and control plane; the plugin and control plane ship together, so no action is needed for a standard deploy.
  • The remaining low-severity hardening item from v0.3.0 (Connect-token origin trusts X-Forwarded-Host) is unchanged and still tracked.

Full commit-level changelog: CHANGELOG.md.