@devries-cameron20 / composio Mirror · read-only / commits / 17525ecb6
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 19:45 UTC

changelog: api security updates (2026-06-04) (#3517)

Adds one concise changelog entry: `docs/content/changelog/06-04-26-security-reliability-hardening.mdx`. Summarizes the post-incident wave of changes, link-forward (no migration-guide links), matching the existing `docs/content/changelog/*.mdx` format. Source of truth + rationale live in Linear PRO-255 (Customer Comms). ### What it covers - **Auth / API keys:** MCP auth required, cookie/session auth removed on v3.1, non-recoverable keys, **scoped API keys** (Proxy Execute opt-in at creation, off by default), auto-added IP allowlists, **MFA available for Dashboard sign-in (off by default)**. - **Connections:** managed-OAuth `initiate` → `link` (Jul 3 cutover), token redaction across **managed + custom** auth configs, Proxy Execute for provider actions. - **Webhooks / Endpoints:** public-URL + signed deliveries; `/api/rerouted/v1` and `/v2` retired (`410`). - **Dashboard:** `platform.composio.dev` → `dashboard.composio.dev` redirect, restoration-period `401`s (API/SDK stay functional), MCP configs view removed (use the MCP API / move to Composio sessions). ### Before merge (reviewer checks) - [ ] Confirm links resolve: Proxy Execute, Webhook Subscriptions API, MCP API reference, Composio sessions. - [ ] Re-confirm live state: MFA is opt-in (not required); destructive-tool denylist was re-enabled. - [ ] Confirm the per-project two-factor toggle is intentionally excluded (distinct from Dashboard MFA). - [ ] Confirm publish date (`2026-06-04`). 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: Rahul Tarak <cryogenicplanet@gmail.com>

palash-c committed Jun 5, 2026 at 02:08 UTC 17525ecb6759adfe480a6323a73b97d86399926a
1 file changed +39
docs/content/changelog/06-04-26-security-reliability-hardening.mdx new
+39
@@ -0,0 +1,39 @@
1 +---
2 +title: "Security, API, and platform updates"
3 +description: "Recent changes across MCP and API authentication, Proxy Execute, connected accounts and triggers, token redaction, webhooks, rate limits, and retired legacy endpoints."
4 +date: "2026-06-04"
5 +---
6 +
7 +A summary of recent security, API, and platform changes you may need to act on. Most won't apply to you, so skim for the ones that do. We are continuing to ship more.
8 +
9 +### Legacy MCP Config routes
10 +- MCP requests now require an API key or `Authorization: Bearer` token. We recommend moving to `composio.create`
11 +
12 +### API Keys
13 +- IP whitelisting, choose which ip address can work from your api keys.
14 +- Scoped API Key are slowly being rolled out with first preset for `proxyExecute`. You will be able to control what actions your api keys can take.
15 +
16 +### Proxy Execute
17 +- Proxy Execute is disabled on `v3` api, please use `v3.1` or update your sdks.
18 +- Proxy Execute is now an opt-in capability on an API key, it is a superset of regular capabilities + proxy execute.
19 +- Proxy Execute requests have a 250MB payload cap.
20 +
21 +### Connections
22 +- Connected-account tokens are redacted in API responses, for both Composio-managed and custom auth configs. Please use [Proxy Execute](https://docs.composio.dev/docs/proxy-execute) instead. If you need this for some special case please reach out to support.
23 +- Reiterating: Composio-managed OAuth connections are moving from `initiate` to `link`. The cutover for remaining organizations is July 3, 2026.
24 +
25 +### Workbench
26 +- Code execution through the remote workbench (`COMPOSIO_REMOTE_WORKBENCH`, `COMPOSIO_REMOTE_BASH_TOOL`) now runs only inside a Composio session. If your code execution stopped working, run it within a Composio session.
27 +
28 +### Webhooks
29 +
30 +- Webhook URLs must be publicly reachable; internal and loopback targets are now rejected.
31 +- Deliveries are now signed (verify the `webhook-signature` header), and there is a new `composio.trigger.disabled` event. Manage subscriptions with the [Webhook Subscriptions API](https://docs.composio.dev/reference/api-reference/webhook-subscriptions).
32 +
33 +### Rate limits
34 +
35 +- Per-IP rate limits now apply; requests that exceed them receive `429` responses.
36 +
37 +### Endpoints
38 +
39 +- The legacy v1 and v2 endpoints, deprecated last year, have now been removed. Any calls to `/v1` or `v2` endpoints now return `410`, please use the class of `v3` and `v3.1` endpoints, if you need a guide to migration you can use [this](https://docs.composio.dev/docs/migration-guide/new-sdk)